Slashdot Mirror

I'm reminded of when they tried to ban Chlorine. It turns out that chlorine is actually quite useful in synthetic organic chemistry. http://www.freedom.org/reports/srchlorine.html

...unless the government wants to put checkpoints on every crossing. which would never happen.

I know what I'm mapping my three keys to: CTRL, ALT, and DEL

"With no power, of which they are possessed, do [legislatures] seem to be less familiar, or to handle less awkwardly, than that of eminent domain. . . . At times they fail, or seem to fail, to distinguish accurately between public and private ends, and if their terms and language be alone consulted, to pervert the power to uses to which it cannot lawfully be applied."

-- Sherman v. Buick
(California Supreme Court, 1867)

who needs Print Screen?

Anyone who runs bleeding edge Linux or Linux on dodgy hardware. More info here

Scroll lock?

Most home and commercial KVMs I've used default to the Scroll Lock key to switch consoles.

While you're at it, get rid of SysRq.

SYSRQ KEY DOCUMENTATION v1.2

Good use for SysRq was introduced long time ago. And still it is *very* useful. Eg. in bleeding-edge 2.6.x kernels

without sysrq key I could have lost some important documents, I can't see a life without this key.

Don't forget Linux's Magic SysRq Key!

I previously thought that I was the most sad, laughable figure in the entire world,

I'll take up position between you two, because I only wish I were that geeky. If I could read the disassembly, I would. Just to learn what-the-hell.

Why's it not respectible to be curious and passionate?

Oh, it involves a computer, I forgot. Best to have an obsession with the Tv, get your brain sucked out, and not get teased.

Living La Verde Lorca.

Disassembly of the 404 bytes being sent by affected systems

The advisory announcing the flaws:
http://www.nextgenss.com/advisories/mssql-udp.txt Various disassemblies and discussions: http://www.snafu.freedom.org/tmp/1434-probe.txt http://www.digitaloffense.net/worms/mssql_udp_worm / http://www.boredom.org/~cstone/worm-annotated.txt

Writeups:
http://www.cnn.com/2003/TECH/internet/01/25/intern et.attack.ap/index.html
http://news.bbc.co.uk/2/hi/technology/2693925.stm
http://story.news.yahoo.com/news?tmpl=story&u=/ap/ 20030125/ap_wo_en_po/na_gen_internet_attack_2
http://bvlive01.iss.net/issEn/delivery/xforce/aler tdetail.jsp?oid=21824

Collected a packet disasembly and some urls here.

Everyone seems to be assuming this is a new use of an old (July) hole; I'm not certain of that. Any facts welcomed, see above url.

this is a new exploit; beginning with a buffer overflow related to the referenced CERT, and then proceeding to another buffer overflow ....

Disassembly of the current probe packets available here for what its worth. This is a nasty little sucker.

dog hair, too

justified under the Commerce Clause. For instance see Heart of Atlanta Motel, Inc. v. United States et al.

I'm working on it... Google surely isn't buying it from me for a chance at $10k though.

Britney pr0n i cant help with. text only. sorry.

Last week, living here in D.C., I heard a news commentator use the phrase "Marshall Law" when describing planes overhead and armed troops around the White House. Putting my head in my hand, I mumbled "whatta idiot".

My wife asked why, I explained to her that generally one considers the suspension of the writ of habeas corpus to be Marshall Law. Mind you, I'm not a lawyer, nor do I play one on T.V.

However, it raised the question in my mind last week, are we going to be compelled by current circumstances to forgoe some freedoms in exchange for not loosing them all ? Opinions ?

In 2.2 and later, using the iproute2 interface, you can route traffic through multiple interfaces and connections will go through in a semi-equalized fasion. "ip route add default nexthop via <addr> dev <device>", and repeat for as many interfaces as you have.

This causes new connections to choose one or the other interfaces, a single connection's traffic goes through one or the other but not both. This is in 2.2 without the DiffServ patches; patched 2.2 and stock 2.4 can make both interfaces be used equally instead of on a per connection basis with the equalize keyword on the ip command.

If you haven't read anyhting about the Snafu Principle check out: An Illustration of the Snafu Principle

Some of my boxen as of several months ago. Both the cabinet and desk are full now. Note the digital grade bungee cord.

Some of my boxen as of several months ago. Both the cabinet and desk are full now. Note the digital grade bungee cord.

Some of my boxen as of several months ago. Both the cabinet and desk are full now. Note the digital grade bungee cord.

I'm not terribly familiar with other implementations so I won't speak of those; but in the case of Linux, you're wrong. The NAT that linux 2.2+ does behaves as stated. See the iproute2 IP Command Reference (the link is to the NAT section).

That's not a reason not to use yer awesome godlike skillz for charitable work. If you don't want to go completely nuts, however, find something you're interested in, something you care about, and find somebody in that interest area that needs you.

The big causes are well served and well funded (and mostly indistinguishable from big business but for selling intangibles), but there's almost certainly some collection of idealists out there who share yourt views who will value and appreciate your contributions. Whatever the cause, from helping educate cute and fuzzy critters to the Toe Jam Liberationist front, there's a protest and/or advocacy group for everything these days. Find one whose rhetoric agrees with you and go to town.

I know whereof I speak; I get paid next to nothing for unholy working hours, and I don't care because I beleive in what I'm doing and I like my work. I can use some help, too. Anybody wanting to donate time, money, hardware, whatever to my cause (which thinks that limited, constitutionally proscribed governemnt, private property rights, and individual freedom are goals worth working for) have a look at our sites, and if you still want to help use the contact info to be found there.

I generally don't post twice on the same story, and I generally don't pay any attention to "party line" regurgitations like this, but I gotta respond. Hopefully those 3 remaining folks who browse at 0 still will read both our comments and judge them almost completely unrelated to the story.

Global climate change is real, it's been happening since there was a globe, and humans' fossil fuel use has had little or no real impact on it. Any changes attributable to humans are dwarfed by those caused by other causes. See this page for a more lucid explaination (with citations) than I can make here after being up so long today.

"...agreements commiting to a policy of reduced fossil fuel use. ...all just talk to appease a few iconoclastic environmentalists." They're not appeased, to judge by the demonstrations still being staged at the ongoing negotiations. It's been and will be more talk, but the goal isn't "saving the planet". I quote one of the very few non-sympathetic persons allowed to observe the proceedings: "The Kyoto Protocol is a prime piece of the embodiment of a massive, grand, global scheme for redistribution of the world's wealth from "abilities" to "needs" -- a scheme which has flamed in the hearts of egalitarians of all stripes and "-isms" for ten thousand years of known human history."

For some reason, I suspect your not-quite on-topic post was motivated by the fact that there's a UN climate change negotiation session happening this week. My response certainly is: I'm involved with an effort to report on those meetings (Daily updates here). Our reports are nearly unique in that we're concerned about not over-reacting to the "urgent problem of global warming". Not a popular attitude... Rather iconclastic by today's standards.

I generally don't post twice on the same story, and I generally don't pay any attention to "party line" regurgitations like this, but I gotta respond. Hopefully those 3 remaining folks who browse at 0 still will read both our comments and judge them almost completely unrelated to the story.

Global climate change is real, it's been happening since there was a globe, and humans' fossil fuel use has had little or no real impact on it. Any changes attributable to humans are dwarfed by those caused by other causes. See this page for a more lucid explaination (with citations) than I can make here after being up so long today.

"...agreements commiting to a policy of reduced fossil fuel use. ...all just talk to appease a few iconoclastic environmentalists." They're not appeased, to judge by the demonstrations still being staged at the ongoing negotiations. It's been and will be more talk, but the goal isn't "saving the planet". I quote one of the very few non-sympathetic persons allowed to observe the proceedings: "The Kyoto Protocol is a prime piece of the embodiment of a massive, grand, global scheme for redistribution of the world's wealth from "abilities" to "needs" -- a scheme which has flamed in the hearts of egalitarians of all stripes and "-isms" for ten thousand years of known human history."

For some reason, I suspect your not-quite on-topic post was motivated by the fact that there's a UN climate change negotiation session happening this week. My response certainly is: I'm involved with an effort to report on those meetings (Daily updates here). Our reports are nearly unique in that we're concerned about not over-reacting to the "urgent problem of global warming". Not a popular attitude... Rather iconclastic by today's standards.

...and possibly offtopic besides.

I've been collecting documentation on the linux 2.2 networking fetures for a while now. What I've got is focused less on Masq/portfw than the neat new routing tricks, but I've got just about everything that's out there, I think.

If there's docs out there I don't have, please tell me about 'em and I'll put 'em up. (email addy on the site).

I've got a collection of all the documentation I've been able to find on the 2.2.x network stack, including the QoS stuff.

It's all at my linux 2.2 site, check it out. Hope it helps.

I've been collecting all the documentation I can find on the new Linux 2.2 networking code for several months; have a look at my Mostly Networking page.

ANK has released his "IP Command Reference" (you can find it on the site) that will probably tell you all you need to know.