> From: owner-openssl-us...@openssl.org On Behalf Of Michael S. Zick > Sent: Tuesday, 01 November, 2011 09:15
> On Mon October 31 2011, Dave Thompson wrote: > > compiled without error, and gave the symptom reported -- > > because CRYPTO_cfb128_1_encrypt treats the length as bits > > > > My copy from the mailing list used: AES_cfb1_encrypt(...) > (Like the title of the post.) > > Can't see how yours got like the above, unless you retyped > the post and your fingers just automatically corrected the > function call being used. > AES_cfb1_encrypt calls CRYPTO_cfb128_1_encrypt, and it is the latter which actually interprets the length argument. I guess I could have detailed that, but I assume(d) anyone who cares about implementation looks at the code. AES_cfb1_ does repeat the comment from CRYPT_cfb128_1_. > > not bytes (apparently only used for AES and Camellia). > > 97 bits is 12 bytes plus 1 bit, and that 'extra' bit > > is 0 and thus 'disappears'. > > > > Yeah, I was thinking of suggesting "man ..." also. > Maybe I should have to have been complete. > There isn't a man page for aes.3, nor camellia.3 which seem to be the only two that work this way. If fact not most of the symmetric algorithms. DES_cfb_encrypt(,,1) puts each bit in a separate byte, so in that case the distinction doesn't occur. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
