frottle: Defeating the Wireless Hidden Node Problem
jasonjordan writes "The West Australian FreeNet Group was the first to go War Flying - and now we've released "frottle" (freenet throttle) - an open source project to control & manage traffic on fixed wireless networks. Such control eliminates the common hidden-node effect even on large scale wireless networks.
frottle works by scheduling client traffic by using a master node to co-ordinate - effectively eliminating collisions!
Developed and tested on the large community wireless network of WaFreeNet, We've found it has given us a significant improvement in network usability and throughput.
"
IMPORTANT: There is a huge security hole in all Mozilla builds thatwas just discovered yesterday. By inserting a properly-constructed URL into anXHTML source file with MIME type application/xml+xhtml, arbitrary code can berun as the client user on his machine. This hole exploits a known bug inMozilla's xml parser, that doesn't properly handle certain character entities(e.g. &#nnn;). If the decimal number inside the character entity is greaterthan 65535 (the maximum legal Unicode value), a buffer overflow is triggeredand arbitrary machine code can be inserted into the running process.
Luckily though, the fix is small, simple,and can be automatically downloaded over the Internet, thanks to Mozilla'sXPI installation facilities. This patch is available from the BrowserSecurity page at data.com and more info is available on Yahoo. Simply click the link, and after a short verification the fixwill install itself.Please install their patch ASAP, before malicious hackers wipe Mozilla offthe web!
Isn't open-source grand? Had this been an Internet Explorer exploit,we wouldn't even know of its existence until about a month after sKr1p7 k1dd1eZ started hacking with it. I applaud the Mozilla team for promptly discoveringand disclosing this bug, and the fine folks at data.com for hosting the fix.
Trolling goatse.cx link. Click at your own risk.
werd up my negro!
a/s/l here. Sorry, adding domain tags to your s
Stupidest troll ever.
It's really a nice concept . I hope they succeed and bring back the uncontrolled internet.
I think so. Check this out:
:)
---
Date: Sat, 20 Apr 2002
From: Bennett Haselton
Subject: Re: Please resolve the censorware conflict.
Any discussion of the Censorware.org controversy has to start from the fact that Michael and the rest of the former CWP are not "equal sides" in this, are not "both right and both wrong", etc.
Michael did not own the Censorware Project and did not do a majority of the work involved, he just hi-jacked the domain name and stole it from the rest of us. The fact that people look at what he did, and look at the response from the rest of the group, and call it "infighting" or "airing dirty laundry" is frankly an insult to the Censorware Project and its work. If the EFF webmaster put the eff.org domain in his own name and then hi-jacked it from the organization, he'd be branded a traitor and a pariah in the Internet community for the rest of his life, and nobody would ever forget what he did. Same if it was the CPSR.org webmaster, the EPIC.org webmaster, or whoever. But if the Censorware Project webmaster does it, we're expected to "work out our differences" with him?
There is an absolute difference between Michael and the rest of us. None of us, despite some personal animosities (not between me and anybody, but between people that I know), would ever, ever do anything like what Michael did. But Michael did it.
It doesn't matter whether or not Michael promotes anti-censorship work in his position as a Slashdot writer; he's hardly making much a difference by saying things that were going to get said anyway, and nothing he does there will ever come close to canceling out the harm he did by shutting down the one-time Censorware Project website.
The only legitimacy that Michael has is through his position as a Slashdot writer; he has just enough writing skills to make his writings sound seductively intelligent to anybody who doesn't know the real story. The fact that Slashdot hired Michael should be deeply embarrassing to them, and is in fact eroding Slashdot's credibility according to comments made by some people who found out about the Censorware.org site. But Slashdot is apparently too deeply wedded that decision to reconsider, and comments from [Michael Sims' direct supervisor] have been more of the same along the lines of "They should work out their differences" instead of acknowledging Michael Sims's utterly disgraceful behavior as compared to the average person. You think Slashdot really believes Michael is trustworthy, after what he did? Do you think they're going to let him put the Slashdot.org domain in his name?
-Bennett
yeeeeeehaaaaaaaawwwwwww!
you can do better