On Thu, Apr 09, 2009, Ger Hobbelt wrote:
>
> Which brings us to Blowfish:
>
> when you compare BF with, say, DES or AES, the latter all have fixed
> width key sizes - by design -, e.g. 64 bits (8 bytes) or 128 bits (16
> bytes). Sure, there's AES-256, but that is a _different cipher_ (okay,
> no
On Tue, Apr 7, 2009 at 8:17 PM, Charles wrote:
> Doh! Thanks guys. I try and use std::strings where possible to keep
> me out of trouble. Stupid. So I should be padding my key? I guess
> this threw me off:
Trouble with string<> is (and with anything that thinks 'string'
instead of 'binary bl
Thanks!!! I solved with EVP_CIPHER_CTX_set_padding(&ctx,0), and padding the
string manually
On Sun, Apr 5, 2009 at 8:07 AM, Ger Hobbelt wrote:
> This has to do with padding, which is at least 1 byte, and always
> ensures input + padding is an integer multiple of the block size.
> Hence 8 inp
On Wed, Apr 08, 2009, Gary Kennedy wrote:
> Specifically, I'm after the version & digestAlgorithms fields of the
> signed-data CMS structure, (read-only at this stage).
>
> How may I go about accessing these fields without 'illegally' including the
> cms_lcl.h header?
>
You can't at present as
