Slashdot Mirror
New Attacks on Spam
AttackOfTheDictionaries writes "Project Honey Pot started operating back in November. The Project provides its participants with a script that generates fake webpages with unique honeypot email addresses. The end result is that Project Honey Pot can connect email harvesters' IP addresses with the spam received by those honeypot email addresses. Which is pretty nifty, but left some people asking how that would help legal attacks on spam. Well, it seems that some lawyer over at SecurityFocus has an answer."
fuppy?
Nobody gives a fucking shit! Huygens images were released earlier...
That won't work. And I think we all know why.
Is it just me or half the story is one big long link??
AttackOfTheDictionaries writes "Project Honey Pot started operating back in November. The Project provides its participants with a script that generates fake webpages with unique honeypot email addresses. The end
result is that Project Honey Pot can connect email harvesters' IP
addresses with the spam received by those honeypot email addresses. Which is pretty nifty, but left some people asking how that would help legal attacks on spam. Well, it seems that some lawyer over at SecurityFocus has an answer."
"WebTV: bringing the Internet into the shallow end of the gene pool since 1995" - Martin Bishop
The dick mini is a small dildo produced by Apple Computer. Designed to captizalize on the ipod mini's halo effect, it provides a compact two inches to match the expectations of the apple community, which is primarily demographized as homosexual men with small penises.
The Linux Revolution Is Dying
./* | grep -v sizeof', I discovered 4 exploitable vulnerabilities in a matter of 15 minutes. More vulnerabilities were found in 2.6 than in 2.4. It's a pretty sad state of affairs for Linux security when someone can find 4 exploitable vulnerabilities in a matter of minutes." - Brad Spengler
In light of the disastrous 2.6 development model that has given sysadmins everywhere a headache by introducing development code into a production line, Linux has signed its own death knell. With more and more people looking to alternatives like FreeBSD 5.x, OS X, and DragonflyBSD, Linux is slowly shovelling the dirt beneath its feet to dig its own grave.
Linux And Windows
Quite simply, the revolution against Windows has run out of steam. While Linux was a viable alternative in the days of Windows 98, when the rallying cry of geeks everywhere was "Down with M$, Linux never crashes," we now have the majority of the Windows userbase running NT-based operating systems. Except in cases of hardware or driver issues, reliability is no longer an issue in the comparison between Linux and Windows.
Eventually, the movement became one of security. In the years after its release, Windows XP was discovered to have several high-profile security flaws. Microsoft underwent a major code audit and released SP2. The rallying cry for OSS was now about security.
However, the community has discovered major flaws in the Mozilla software suite, including bugs marked "confidential" for years at a time. Additionally, major security holes have been appearing in the 2.6 line of Linux kernels, some having existed for years and affecting the 2.4 line. Declaring Linux to be the secure alternative is no longer as true.
Worst of all, the Linux kernel developers have no clear process, nor any clear contact person, when it comes to security issues.
Evidence: http://lwn.net/Articles/118251/
Evidence: Long-time shell-provider SDF used Linux until they got hacked into. Now, it's a 64-bit version of NetBSD.
Evidence: PaX discovered the mlockall hole. It was fixed in PaX for two years. Linux just now (2005) caught up.
Evidence: "Using 'advanced static analysis': 'cd drivers; grep copy_from_user -r
The New Linux Development Model
With the 2.6 line of kernels, a new model has been adopted that is considered easier for the kernel developers. Instead of branching a 2.7 line, following the model of odd-numbered version numbers denoting development code, everything is now being thrown into 2.6.
"Not all 2.6.x kernels will be good; but if we do releases every 1 or 2 weeks, some of them *will* be good. The problem with the -rc releases is that we try to predict in advance which releases in advance will be stable, and we don't seem to be able to do a good job of that. If we do a release every week, my guess is that at least 1 in 3 releases will turn out to be stable enough for most purposes. But we won't know until after 2 or 3 days which releases will be the good ones." -- Ted T'So
In other words, this Linux kernel developer believes it is perfectly fine for one in three kernels of the stable line to actually be stable. The new development process is anti-user. "Release early, release often" has outlived its reliability and applicability to the real world.
The excuse given is that Linus is only one man, and there are only 24 hours in a day. If that is true, than Linus needs to address this shortcoming of the process; otherwise, the process is poorly managed.
The Community Has Regurgitated Itself
In a frenzy of newbies, the Linux community has grown, with Slashdot as its rallying center. The cycle of self-feeding groupthink has created a userbase unable to see outside its own perceptions. This leads to unrealistic attitudes about the safety and stability of Linux and its applicability to various solutions.
Contrast to the BSD community which employs a more academic approach.
Google now returns crap web pages! As if it wasn't bad enough that google doesn't filter out the retail sites for non-retail searches.
Always going forward, 'cause we can't find reverse.