There are biases throughout the whole RC4 keystream, not just in the first few bytes. RC4 is totally broken.
Re:Teensy weensy crypto
by ultramancool on Thursday November 12, 2015 @06:36PM
(#10556982)
If you cannot have something continue to produce output though those periodic biases cannot be obtained, To my knowledge you need a quite large amount of output to exploit them.
So for encrypting a single short message, where an attacker is unable to obtain more output, this should be sufficient for such a purpose.
Still, I wouldn't use it at all, there are other micro alternatives like TweetNaCl which offer a far higher degree of security.
> So for encrypting a single short message, where an attacker is unable to obtain more output, this should be sufficient for such a purpose.
This is fairly vacuous as there are tons of really broken cryptosystems for which this is true; futhermore if you are going to only send a single short message with a given key, an OTP could probably be described in 140 characters of English prose and requires no machine to implement.
It's not vacuous, but there is a history of cryptosystems that have tried and failed to sidestep that RC4 weakness by burning off keystream, so it's worth being careful about it.
Re:Teensy weensy crypto
by kybernetikos on Friday November 13, 2015 @04:18AM
(#10558789)
"This use-case" indicates to me a single message encrypted with a single passphrase.
RC4 was known to not have this "head room" for a while, and now is largely broken.