March 12, 2003
UPI: Pentagon Papers Leaker Seeks Leaks on Iraq

by Mark Benjamin

WASHINGTON -- Daniel Ellsberg, who in 1971 leaked the Pentagon Papers, on Tuesday called on government officials to leak documents to Congress and the press showing the Bush administration is lying in building its case against Saddam Hussein.

Ellsberg, an ex-Marine and military analyst, said he held out hope that exposing alleged lies by the Bush administration could still avert an unjust war. He warned that whistleblowers may face ruin of their careers and marriages and be incarcerated.

"Don't wait until the bombs start falling," Ellsberg said at a Tuesday press conference in Washington. "If you know the public is being lied to and you have documents to prove it, go to Congress and go to the press."

Ellsberg did not leak the Pentagon Papers to the New York Times until 1971, although he says he had information in the mid-1960s that he now wishes he had leaked then.

"Do what I wish I had done before the bombs started falling" in Vietnam, Ellsberg said. "I think there is some chance that the truth could avert war."

The thousands of pages in the Pentagon Papers showed the government's secret decision-making process on Vietnam since the end of World War II. Their publication -- the government sued and lost to prevent it -- is widely credited with helping to turn public opinion against the war in Southeast Asia.

Ellsberg's press conference comes a little more than a week after the London Observer reported on what it said is a top-secret memo showing that the United States planned to spy on U.N. delegates to gain an advantage in the debate over Iraq.

The Observer reported the electronic memo dated Jan. 31, by high-ranking National Security Agency operative Fank Koza, says the agency is "mounting a surge" of intelligence activities mostly focused on U.N. Security Council members for "information that could give U.S. policy-makers an edge in obtaining results favorable to U.S. goals or to head off surprises."

NSA spokesman Patrick Weadon wouldn't comment on the authenticity of the e-mail memorandum. "We have no statement," he said.

U.N. ambassadors have mostly shrugged off the memorandum as reflecting the regular course of business at the United Nations.

Ellsberg said this story on spying at the United Nations is potentially more significant than the Pentagon Papers because it comes before a war has begun and it shows a desperate Bush administration. "This leak is potentially more significant than the release of the Pentagon Papers, since it is extraordinarily timely," Ellsberg said.

This past Sunday, the Observer reported that an employee at the top-secret British Government Communications Headquarters had been arrested following publication of the story. Ellsberg said reporters at the Observer told him the 28-year old woman arrested was not the source of the leak.

A second U.S. diplomat resigned yesterday in protest against the Bush administration's war stance. John H. Brown, who served in the diplomatic corps since 1981, said Bush's disregard for the views of other nations was giving birth to "an anti-American century." Last month, a senior U.S. diplomat based in Athens, political counselor John Brady Kiesling, resigned with similar complaints.

Last week, Mohamed ElBaradei, director general of the International Atomic Energy Agency, rejected a Bush administration claim that Iraq had tried to purchase high-strength aluminum tubes to use in centrifuges for uranium enrichment.

Copyright © 2001-2003 United Press International

Pentagon Papers Leaker Seeks Leaks on Iraq

Posted by Brian Stefans at March 12, 2003 04:22 PM
Comments

Each Stack Frame represents a function. The bottom frame is always the main function, and the frames above it are the other functions that main calls. At any given time, the stack can show you the path your code has taken to get to where it is. The top frame represents the function the code is currently executing, and the frame below it is the function that called the current function, and the frame below that represents the function that called the function that called the current function, and so on all the way down to main, which is the starting point of any C program.

Posted by: Christopher on January 18, 2004 09:14 PM

Note first that favoriteNumbers type changed. Instead of our familiar int, we're now using int*. The asterisk here is an operator, which is often called the "star operator". You will remember that we also use an asterisk as a sign for multiplication. The positioning of the asterisk changes its meaning. This operator effectively means "this is a pointer". Here it says that favoriteNumber will be not an int but a pointer to an int. And instead of simply going on to say what we're putting in that int, we have to take an extra step and create the space, which is what does. This function takes an argument that specifies how much space you need and then returns a pointer to that space. We've passed it the result of another function, , which we pass int, a type. In reality, is a macro, but for now we don't have to care: all we need to know is that it tells us the size of whatever we gave it, in this case an int. So when is done, it gives us an address in the heap where we can put an integer. It is important to remember that the data is stored in the heap, while the address of that data is stored in a pointer on the stack.

Posted by: Phillipa on January 18, 2004 09:14 PM

When the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.

Posted by: Paschall on January 18, 2004 09:14 PM

When the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.

Posted by: Walter on January 18, 2004 09:14 PM

This will allow us to use a few functions we didn't have access to before. These lines are still a mystery for now, but we'll explain them soon. Now we'll start working within the main function, where favoriteNumber is declared and used. The first thing we need to do is change how we declare the variable. Instead of

Posted by: Blanche on January 18, 2004 09:14 PM
-->