Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Debian 6.0 "Squeeze" released (

slushdork writes: After 24 months of constant development, the Debian Project is proud to present its new stable version 6.0 (code name "Squeeze"). Debian 6.0 is a free operating system, coming for the first time in two flavours. Alongside Debian GNU/Linux, Debian GNU/kFreeBSD is introduced with this version as a "technology preview. Debian supports nine architectures, from palmtops and handheld systems to supercomputers, and on nearly everything in between. The Debian websites also have a new look!

Submission + - Debian 6.0 Released In Linux, FreeBSD Flavors ( 1

itwbennett writes: After two years of work, the Debian Project has announced the release of Debian 6.0. 'There are many goodies in Debian 6.0 GNU/Linux, not the least of which is the new completely free-as-in-freedom Linux kernel, which no longer contains firmware modules that Debian developers found troublesome,' says blogger Brian Proffitt. And in addition to Debian GNU/Linux, Debian GNU/kFreeBSD is introduced as a technology preview. 'Debian GNU/kFreeBSD will port both a 32- and 64-bit PC version of the FreeBSD kernel into the Debian userspace, making them the first Debian release without a Linux kernel,' says Proffitt. 'The Debian Project is serious about the technology preview label, though: these FreeBSD-based versions will have limited advanced desktop features.' Installation images may be downloaded right now via bittorrent, jigdo, or HTTP.

Comment Re:They should more to a more civilized country (Score 2, Insightful) 392

If I do work today I don't continue getting paid for it 70 years after I'm dead... why should you?

Although I completely agree that the extention of copyright to ever-increasing terms is scandalous and that it should be restricted to the original 10-20 years, I don't buy the argument above. Say I build a house today that I rent out and which generates income for me during my lifetime - should my family be denied that income (or even the house itself!) after I die?

Similarly, if a writer publishes a book today, and then dies a year from now, his family should be able to benefit from his work for a reasonable period of time.

Obviously, the house is a tangible asset while a work of art is not (at least, not in the case of books), but you cannot simply state that my descendants shouldn't receive any income from either asset after I die.

Comment You say either, I say either... (Score 1) 307

It doesn't matter either way. Barring some unknown bug in the SSH implementations (or, even more unlikely, the underlying SSH 2 protocol, or, yet even more unlikely, the under-underlying encryption mechanisms), you can stay logged in or keep re-loging in - both methods should provide no information to an attacker.

Even if there were unknown bugs, you still wouldn't be able to decide: staying logged in gives the attacker more encrypted material to analyze from the same session & keys. Re-loging in every 10 minutes gives them more handshake data.

By the way, I hope that hosts.allow is not the only way you're protecting your servers from the "big bad internet"...

Slashdot Top Deals

Nothing motivates a man more than to see his boss put in an honest day's work.