Re: Limiting RC4 to "40 bit" strength

From: Roger Schlafly (rogersc1_at_mindspring.com)
Date: 05/19/04 

Date: Tue, 18 May 2004 22:31:24 -0700

"David Wagner" <daw@taverner.cs.berkeley.edu> wrote
> If you're combining a password (key) + unique string (nonce)
> to form the key-input to RC4, you absolutely must hash them
> before feeding to RC4. Simple concatenation is a really bad
> idea, and RC4 is not secure when used with simple concatenation.

Why not? Do you have a reference for that?

Relevant Pages

  • Re: Is RC4 a good choice?
    ... do you mean the concatenation of the master key K and the IV? ... >got WEP in trouble. ... with RC4 is what gives cause for concern and allows the attack. ... And this brilliant attack used the above factors to do damage. ...
    (sci.crypt)
  • Re: Limiting RC4 to "40 bit" strength
    ... to form the key-input to RC4, you absolutely must hash them ... before feeding to RC4. ... and RC4 is not secure when used with simple concatenation. ...
    (sci.crypt)
  • Re: Limiting RC4 to "40 bit" strength
    ... and RC4 is not secure when used with simple concatenation. ... Do you have a reference for that? ... The Roos weak-key attack. ...
    (sci.crypt)
  • Re: Microsoft.VisualBasic.Strings.Asc ?
    ... the rc4 algorithm ... RC4 is an old algorithm and is now obsolescent. ... learning exercise, being very easy to program, or for mild security. ... You should concatenate and hash, ...
    (microsoft.public.dotnet.languages.csharp)
Quantcast