Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

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"...

Comment What about non-HTTP? (Score 5, Interesting) 362

I'm a Comcast "customer" in an affected "market" (Colorado). How will this affect DNS resolution requests for non-HTTP purposes? There is no way for the Comcast DNS servers to know what a DNS name resolution request is for: it could be for HTTP, or it could be for SSH, FTP, etc. So if I mis-type an FQDN hostname in an SSH command, will the DNS resolution request now suceed? Previously SSH would fail with a "cannot resolve hostname" error or something similar. Will it now try to connect with SSH to the Comcast "domain helper" servers? What about its effects on local DNS caching servers (e.g. dnsmasq)?

Also, this statement from Comcast's blog is blatantly false:

Despite the fact that web addresses are easier to remember than their IP address counterparts, sometimes you mistype an address. Let's say you type in http://www.comtcas.com/ (instead of http://www.comcast.com./ Normally you then sit and wait for the Web browser to time out, then you receive an error message that the site does not exist, and then you have to retype the correct address.

Normally you would *never* "sit and wait for the Web browser to time out" (well, these *are* Comcast's DNS servers after all, so in this specific case it might be true). Normally, your browser would get a DNS resolution failure and show you a built-in error page instantaneously. Now, on the other hand, you have to wait until your browser goes off and loads a page of Comcast ads.

Domain Helper my a$$!

Slashdot Top Deals

Beware of Programmers who carry screwdrivers. -- Leonard Brandwein

Working...