In Arlington County, Virginia of the mid-1970's, 7th and 8th grade math students were treated to a week-long exploration of BASIC programming, complete with access to a HP 9830A, and an HP 7260A Optical Mark Reader. We used HP Educational BASIC Cards. So, the drill was: write your program on paper, transcribe it to the cards with #2 pencil, then get in line to put your cards in the reader. Inevitably the Reader would choke on a card, and issue a "Pick Fail" error. That could be due to a damaged card or to the number of erasures and rewrites on a card. Pick Fails were always accompanied by three honks from an alarm inside the Reader. Moans from students waiting in line for card reading usually followed. The best you could hope for was one iteration of your program per day, but realistically you got 2 or 3 runs during programming week, what with all the Pick Fails.
The People's Daily article mentions that the TLDs.MIL,.GOV and.EDU will be created under.CN. The fact that they have chosen not to place their.COM and.NET under.CN suggests a desire on their part to challenge the authority of ICANN.
Also, there are other ways to investigate image files.
I've experimented with Provos' steganographic tool, outguess. I encoded a short message in a.jpg using the default option to foil detection by preserving statistical properties of the cover medium. Sure enough, the companion detection tool, stegdetect was not able to detect that a message was concealed.
Then, on a hunch, I converted the original and altered.jpgs to.bmps, and examined them side by
side using od -c | less. In the.bmp produced from the altered.jpg, I noted repeated 'senseless variations' in color values, usually pixel triplets of 377-376-377 (octal), as my sample pic was an object on a white background.
Of course you would need the original image to definitively prove alteration of content. But this could be reduced to process and used to sift through content for likelihood of alteration. Such a tool might prove beneficial as a substitute for blunt instruments such as Carnivore.
ISPs have an important opportunity here. They could demand that surveillance systems include accountability measures, such as monitoring statistics made available to customers. It should be possible to make these stats informative enough to satisfy customers' desire for information, yet not so specific as to compromise an investigative strategy.
why is it that when a
Linux group does it, it's the responsiblity of a single person who is quickly singled out, but when the group from Redmond does it, suddenly it's the entire corporation that is to blame?
Free software and open-source communities value individual contribution and responsibility. Missteps within the community are associated with the responsible individuals. That is a strength of this kind of community structure.
Corporate environments devalue individual responsibility. It is appropriate to hold the whole entity responsible. Microsoft encourages this line of thinking by pointing the finger at the ATL.
In fact, this is part of the nature of a corporation. In legal terms it is equivalent to a person, and its formation is with the intent of shielding the persons who are part of it.
Naturally we must consider M$ innocent until proven guilty on this. But if they are guilty, they are guilty as a whole, unless they choose to
identify the individuals responsible. Such a move would necessitate a major realignment in their corporate culture.
in my experience this sort of thing crops up a lot in group development projects, an area where python would do well. I'm all right with language-imposed formatting restrictions since it saves developers' time of understanding and reformatting each others' code.
Slashdot Mirror
In Arlington County, Virginia of the mid-1970's, 7th and 8th grade math students were treated to a week-long exploration of BASIC programming, complete with access to a
HP 9830A, and an HP 7260A Optical Mark Reader. We used HP Educational BASIC Cards.
So, the drill was: write your program on paper, transcribe it to the cards with #2 pencil, then get in line to put your cards in the reader. Inevitably the Reader would choke on a card, and issue a "Pick Fail" error. That could be due to a damaged card or to the number of erasures and rewrites on a card. Pick Fails were always accompanied by three honks from an alarm inside the Reader. Moans from students waiting in line for card reading usually followed. The best you could hope for was one iteration of your program per day, but realistically you got 2 or 3 runs during programming week, what with all the Pick Fails.
The People's Daily article mentions that the TLDs .MIL, .GOV and .EDU will be created under .CN. The fact that they have chosen not to place their .COM and .NET under .CN suggests a desire on their part to challenge the authority of ICANN.
Also, there are other ways to investigate image files.
.jpg using the default option to foil detection by preserving statistical properties of the cover medium. Sure enough, the companion detection tool, stegdetect was not able to detect that a message was concealed.
.jpgs to .bmps, and examined them side by
.bmp produced from the altered .jpg, I noted repeated 'senseless variations' in color values, usually pixel triplets of 377-376-377 (octal), as my sample pic was an object on a white background.
I've experimented with Provos' steganographic tool, outguess . I encoded a short message in a
Then, on a hunch, I converted the original and altered
side using od -c | less. In the
Of course you would need the original image to definitively prove alteration of content. But this could be reduced to process and used to sift through content for likelihood of alteration. Such a tool might prove beneficial as a substitute for blunt instruments such as Carnivore.
Thoughts?
Dug
ISPs have an important opportunity here. They could demand that surveillance systems include accountability measures, such as monitoring statistics made available to customers. It should be possible to make these stats informative enough to satisfy customers' desire for information, yet not so specific as to compromise an investigative strategy.
-Dug
Kind of amusing that Citizens Against Government Waste aren't running IIS considering that they get some of M$'s $...
Here is what netcraft has to say...
The site www.cagw.org is running Rapidsite/Apa-1.3.14 (Unix) FrontPage/4.0.4.3 mod_ssl/2.7.1 OpenSSL/0.9.6 on IRIX
why is it that when a
Linux group does it, it's the responsiblity of a single person who is quickly singled out, but when the group from Redmond does it, suddenly it's the entire corporation that is to blame?
Free software and open-source communities value individual contribution and responsibility. Missteps within the community are associated with the responsible individuals. That is a strength of this kind of community structure.
Corporate environments devalue individual responsibility. It is appropriate to hold the whole entity responsible. Microsoft encourages this line of thinking by pointing the finger at the ATL.
In fact, this is part of the nature of a corporation. In legal terms it is equivalent to a person, and its formation is with the intent of shielding the persons who are part of it.
Naturally we must consider M$ innocent until proven guilty on this. But if they are guilty, they are guilty as a whole, unless they choose to
identify the individuals responsible. Such a move would necessitate a major realignment in their corporate culture.
so, we know that a.root is an RS/6000 S80, and
f.root is served by twin es40 compaq alphas.
just curious.. anyone know what the other 12 are running?
-dug
in my experience this sort of thing crops up a lot in group development projects, an area where python would do well. I'm all right with language-imposed formatting restrictions since it saves developers' time of understanding and reformatting each others' code.