A year ago (November 2005) there was a flurry of military silly string articles (LifeHacker, Schneier, others) all leading back to a cockeyed.com article, which quoted a soldier saying they used it for locating tripwires. The site didn't leave the content up for long, but it's preserved at the Internet Archive.
In the 90s I saw a demo of a single-pane eyeglass-free steroscopic display, made by Dimension Technologies in Rochester NY. Here's one of their patents: http://www.patentstorm.us/patents/6040807.html
At the time, CRTs with LCD shutter glasses were cheaper, and better for screen size and resolution. But the eyeglass-free feature was remarkable.
The only thing left is to follow the zeitgeist and produce a postmodern deconstructed paranoid conspiracy Star Trek in which all previous assumptions about what's really happening are blown away, revealing a whole new layer of technology and society manipulating the public face of the Star Trek world for its own ends. Put a whole new spin on the rise and fall of empires, the attacks of puppetmasters and Borg, and create some new backstories for the most unusual events including time travel, alternate universe, and yet-another omnipotent-being stories. It's basically Star Trek meets Foundation. The main challenge is to create likable characters within this shadow world, and avoid technology deus ex machina.
your licensing policy, as summarized in the
RHEL FAQ:
Except for a few components provided by third parties (for example, Java) all the code in Red Hat products is open source and licensed under the GPL (or a similar license, such as the LGPL). So you always have free access to the source code. In fact you can download it from our FTP servers at any time. However, Red Hat does not provide free access to the binaries of Red Hat Enterprise Linux, and these, combined with an annual subscription to Red Hat Network, access to upgrades, and a selected support services, are the components that Red Hat bundles into each Red Hat Enterprise Linux solution. Since every Red Hat Enterprise Linux product includes support for the system on which it is installed, Red Hat supplies the products with a per-system usage/support subscription. This simple model ensures that systems which useRed Hat Enterprise Linux are able to access the maintenance, services and product upgrades to which they are entitled. Of course, as mentioned before, this has no impact on your access to the Red Hat Enterprise Linux source code.
2. b)
You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
Unfettered access to source code does not eliminate your users' rights to the derived works,
including right to copy your binaries. Or is it
your position that by agreeing with your service agreement a user waives their rights to copy under the GPL? Even if that's the case, doesn't distribution solely under those terms violate your
license to GPLd works?
A number of systems at the University of Rochester
were compromised during the Shimomura incident.
The compromises included deliberate destruction of
log files. So which is it:
Deliberate destruction of log files doesn't count as deliberate destruction according to KM?
Now you have had a long time to think about ethics
in general and the system-cracker ethic in particular. You expended quite a bit of creativity breaking into systems AND covering your tracks (deleting log files, etc).
What would you like to say now about your new perspective (if any) on the ethics of asserting that "justing exploring" is not damaging, and the ethics of damaging whatever audit trail exists?
How would you describe yourself -- repentant, chastened, defiant, what?
And, finally, how constrained are your remarks -- are there legal consequences (due to probation or parole) if you say "the wrong thing" -- or are you as free as the rest of us to shoot your mouth off? (Obviously there are market consequences to any remarks you may make, as you sell your services and books.)
Actually, I thought that you could only
asymptotically approach the event horizon
(time/space would dilate and you'd never actually
get there).
Of course, you'd be torn apart by tidal forces
and horrible stuff flowing around you, so "observation" is somewhat hypothetical (but
interesting).
His previous book "The Great Reckoning" was
fascinating reading, even though the particulars
never came to pass. (For example, he predicted
that economic leadership would pass to Japan.)
But his "big picture" was provocative, so I will
be looking for more thoughtful provocation in the
new book (though I will discount its predictive power).
No, Microsoft has embraced and extended Kerberos:
you can use a W2K Kerberos server with both Unix
and Windows clients. You can't use a non-Microsoft Kerberos server and support the extra Microsoft baggage for W2K clients.
(Baggage recently documented by Microsoft,
under non-disclosure.)
I have been involved with protest arrests,
and have personally witnessed
both exemplary police behavior and
police misconduct. I see both sides.
I'd like to direct your attention to the
eyewitness report
of a local radio commentator
who observed Philly police dealing with an organized
disturbance with extreme forbearance
(e.g. not responding to protesters assulting them
in the course of their duties).
Seriously now, considering that every packet has a source and destination IP address, adding some instrumentation to verify that source addresses are not spoofed has zero impact on privacy.
It does raise the bar, so the next steps in the cat&mouse game include ever-more-diffuse distributed attacks to avoid more ever-more-watchful intrusion detection and traceback mechanisms. Is that a bad thing? No -- it is a good thing to make successull attacks more challenging.
A little more background reading:
Stefan Savage, Practical Network Support for IP Traceback a technique for tracing, but requires a little packet marking/mangling which makes it unlikely to be adopted. Clever, though, I'm sure some of the ideas will fold into itrace.
Other efforts in traceback involve perturbing the source of floods (e.g. by hop-by-hop reverse flooding) and watching the statistical properties of the flood at each step.
Slashdot Mirror
The DEC DECstation 3100 had a 16.7-MHz R2000 MIPS Technologies processor and ran Ultrix.
It was introduced in early 1989.
The Sun SPARCstation 1 had a 20-MHz Sun SPARC processor.
It was introduced in late 1989.
It was a more successful product line.
Whatever you do, don't encode the killer joke in a communicable germ!
A year ago (November 2005) there was a flurry of military silly string articles (LifeHacker, Schneier, others) all leading back to a cockeyed.com article, which quoted a soldier saying they used it for locating tripwires. The site didn't leave the content up for long, but it's preserved at the Internet Archive.
In the 90s I saw a demo of a single-pane eyeglass-free steroscopic display, made by Dimension Technologies in Rochester NY. Here's one of their patents: http://www.patentstorm.us/patents/6040807.html
At the time, CRTs with LCD shutter glasses were cheaper, and better for screen size and resolution. But the eyeglass-free feature was remarkable.
I see the company is still around and still markets 2D/3D displays. http://www.dti3d.com/content/view/22/89/
The only thing left is to follow the zeitgeist and produce a postmodern deconstructed paranoid conspiracy Star Trek in which all previous assumptions about what's really happening are blown away, revealing a whole new layer of technology and society manipulating the public face of the Star Trek world for its own ends. Put a whole new spin on the rise and fall of empires, the attacks of puppetmasters and Borg, and create some new backstories for the most unusual events including time travel, alternate universe, and yet-another omnipotent-being stories. It's basically Star Trek meets Foundation. The main challenge is to create likable characters within this shadow world, and avoid technology deus ex machina.
should have never named that machine sco.fnal.gov
- your licensing policy, as summarized in the
RHEL FAQ:
- appears to violate the
GNU General Public License:
Unfettered access to source code does not eliminate your users' rights to the derived works, including right to copy your binaries. Or is it your position that by agreeing with your service agreement a user waives their rights to copy under the GPL? Even if that's the case, doesn't distribution solely under those terms violate your license to GPLd works?A number of systems at the University of Rochester were compromised during the Shimomura incident. The compromises included deliberate destruction of log files. So which is it:
Actually, I thought that you could only asymptotically approach the event horizon (time/space would dilate and you'd never actually get there). Of course, you'd be torn apart by tidal forces and horrible stuff flowing around you, so "observation" is somewhat hypothetical (but interesting).
His previous book "The Great Reckoning" was fascinating reading, even though the particulars never came to pass. (For example, he predicted that economic leadership would pass to Japan.) But his "big picture" was provocative, so I will be looking for more thoughtful provocation in the new book (though I will discount its predictive power).
See http://slashdot.org/articles/00/06/28/0042228.shtm l for recent SlashDot discussion.
I'd like to direct your attention to the eyewitness report of a local radio commentator who observed Philly police dealing with an organized disturbance with extreme forbearance (e.g. not responding to protesters assulting them in the course of their duties).
It does raise the bar, so the next steps in the cat&mouse game include ever-more-diffuse distributed attacks to avoid more ever-more-watchful intrusion detection and traceback mechanisms. Is that a bad thing? No -- it is a good thing to make successull attacks more challenging.
A little more background reading:
Stefan Savage, Practical Network Support for IP Traceback a technique for tracing, but requires a little packet marking/mangling which makes it unlikely to be adopted. Clever, though, I'm sure some of the ideas will fold into itrace.
Robert Stone, CenterTrack: An IP Overlay Network for Tracking DoS Floods A tool for ISPs to build monitoring networks without making every component cooperate. Hmmm... I wonder if Carnivore has remote tunnels built in?
Other efforts in traceback involve perturbing the source of floods (e.g. by hop-by-hop reverse flooding) and watching the statistical properties of the flood at each step.