This is contrary to the specification: "The total length of an Enhanced Provider symmetric key and its salt value cannot be greater than 128 bits." So, I think this salt value should not have any influence, as the bits you can set are the trailing bits between the reduced key size and the one the algorithm requires.
_____ From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Bugcollect.com Sent: Sunday, May 08, 2011 12:23 AM To: openssl-users@openssl.org Subject: Re: Initialization Vector for EVP_rc4() ? I forgot to mention: the original application uses the Enhanced Cryptography Provider (http://msdn.microsoft.com/en-us/library/aa386986%28v=vs.85%29.aspx <http://msdn.microsoft.com/en-us/library/aa386986(v=vs.85).aspx> ) which supports 128 bit RC4 keys. The application sets the RC4 cipher from a full 128 bit key and a 128 bit salt. On May 6, 2011, at 10:41 PM, Bugcollect.com wrote: Hello, I need to exchange encrypted content with an existing application on Windows with an RC4 key that is salted as per http://msdn.microsoft.com/en-us/library/aa387782%28v=vs.85%29.aspx (KP_SALT_EX). Note that this is not a passphrase and salt key derivation, but a cipher initialized with some a known key and known initialization vector, similar to a block cipher. I think technically RC4 does not have an IV, but what is the equivalent operation I can perform in openssl to get the cipher in the desired state? Specifying the salt as the iv param in EVP_EncryptInit does not work. TIA, ~ Remus ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
