Hmm... Or, if you assume random words, I suppose you can get 32.4 bits of entropy (based on 12.9 bits of entropy per word), which is still easy enough to crack if you have the hash.
We faced the same problem when generating random passwords for users and decided that the best method was to generate two short (4-6 characters) english words with a number at the end. This creates passwords such as swimeasy12, turnright62, sidedoor81, etc. These proved to be very easy to rememeber...
Of course they were easy to remember! These passwords only have, on average, 22 bits of entropy. That's less entropy than you get out of 7 random digits! (Assuming 5 characters per word and 1.6 bits of entropy per English character, which is more optimistic than some other estimates.)
I think that any given pixel on a digital camera can detect ONE of either red, green, or blue, but when you save a TIFF image, you borrow colour information from adjacent pixels, causing the file size to increase.
The other half is telling them "write it yourself" when they complain about the software. That too is easier with open source, compared to proprietary products.
I think if the "write it yourself" attitude completely disappeared, there would be no large open-source projects, because all the developers would burn out due to frustration.:-)
These days cars and highways for a large part have become safe enough for 150-160 KPH.
It doesn't work that way.
Kinetic energy is proportional to the square of your speed. This means that if you're driving at 160 KPH, you have over 3.1 times the kinetic energy as when you're driving at 90 KPH. In the same amount of time as it takes to reduce your speed from 90 KPH to zero, you will not even reduce your speed to 130 KPH if you start at 160 KPH.
If you're involved in a collision at even 100 KPH, there's quite a good chance that you'll be dead or seriously injured.
I doubt that cars and roads have improved that much. People's reaction times certainly haven't. Unless you have some hard evidence to back up your safety claims, I think you're talking out of your ass, regardless of your +5, Insightful mod.
Consumers' best interests would be best served my using NO crypto. All that crypto hardware/software costs money to develop and manufacture. Guess who pays for it in the end?
Be quiet. It's one thing to expect them to release interface documentation for their cards, but that's by far more useful to the community than having them write some GUI. If interface specs are released, we can write our own GUIs.
Slashdot Mirror
Hmm... Or, if you assume random words, I suppose you can get 32.4 bits of entropy (based on 12.9 bits of entropy per word), which is still easy enough to crack if you have the hash.
If you want to generate cryptographically strong passwords, see http://www.diceware.com/,
Of course they were easy to remember! These passwords only have, on average, 22 bits of entropy. That's less entropy than you get out of 7 random digits! (Assuming 5 characters per word and 1.6 bits of entropy per English character, which is more optimistic than some other estimates.)
Quick! Somebody start a petition to demand that Intel drop the JMP instruction from its processors! It's an abomination!
I think that any given pixel on a digital camera can detect ONE of either red, green, or blue, but when you save a TIFF image, you borrow colour information from adjacent pixels, causing the file size to increase.
Dupes won't go away until they start adversely affecting /.'s bottom line.
IIRC, FTP pre-dates TCP.
Part of the reason for that is that any teenager can complain and make half-baked "suggestions", even if they barely have any idea of what they're talking about (written by Yours Truly over 4 years ago).
I think if the "write it yourself" attitude completely disappeared, there would be no large open-source projects, because all the developers would burn out due to frustration. :-)
heh. Just make sure you don't hit Enter too soon...
That's what is known as "too late". At best, that'll give us one chance to do something right that we've never ever done before.
Copywriting is not the same as copyrighting.
Heh. rm -rf / gets to your home directory quicker than you would think...
I guess I missed the ~ part. I parsed another, very similar sig here, so after a quick glance, I just assumed they were identical.
s/a lawsuit/criminal charges/
It doesn't work that way.
Kinetic energy is proportional to the square of your speed. This means that if you're driving at 160 KPH, you have over 3.1 times the kinetic energy as when you're driving at 90 KPH. In the same amount of time as it takes to reduce your speed from 90 KPH to zero, you will not even reduce your speed to 130 KPH if you start at 160 KPH.
If you're involved in a collision at even 100 KPH, there's quite a good chance that you'll be dead or seriously injured.
I doubt that cars and roads have improved that much. People's reaction times certainly haven't. Unless you have some hard evidence to back up your safety claims, I think you're talking out of your ass, regardless of your +5, Insightful mod.
Are you taking precautions against ESD?
The code above executes "rm -rf /".
Consumers' best interests would be best served my using NO crypto. All that crypto hardware/software costs money to develop and manufacture. Guess who pays for it in the end?
Why the hell shouldn't that be done? (Unless you're referring to using Python. :-) )
Be quiet. It's one thing to expect them to release interface documentation for their cards, but that's by far more useful to the community than having them write some GUI. If interface specs are released, we can write our own GUIs.
I think (hope) that's what that winking smiley ";)" was for...
Can't they just filter traffic from the offending IP address and wait for the customer to call them? Of course, that's not necessarily better...
I called my politician and asked that he demand that the name "HAL" be banned. He said that he was sorry, but he was afraid he can't do that.
I believe it *is* the pronoun. The Doctor's name isn't "who"; he's simply The Doctor.
It's probably fixed now. The /. editors do make minor changes to the articles...
This has been addressed in RFC 3675