Sure would... that is why I use the binary version! (c: (8 bytes ivheader +
8 bytes IV + 16 bytes MD5 + 8 bytes padding = 40 bytes)
Anyone else??? Keep the ideas coming!
> -----Original Message-----
> From: Colin Viebrock [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 25, 2001 11:19 AM
> To: Scott Meeuwsen
> Cc: [EMAIL PROTECTED]
> Subject: Re: OpenSRS encryption algorithm frustration...
>
>
> [Thu, 25 Jan 2001] Scott Meeuwsen said:
>
> > Notes:
> > -I am sending 'RandomIV' + IV as a prefix to the encrypted message
> > -I am not decrypting challenge. I simply get the md5 hash and
> send it back
> > encrypted
> > -My total challenge response length is 40 which I believe is correct
> > -I am using JCE 1.2 with 'Blowfish/CBC/PKCS5Padding' or
> > 'DES/CBC/PKCS5Padding'
> > -Tried different DES and blowfish keys by 'Generating new private key'
> > -I have tried ABA, BouncyCastle, and Sun encryption providers
> > -Key is mangled before use according to algorithm in PHP code
>
> I'm no Java expert, but Perls' MD5 returns binary data (i.e. a 16-byte
> string) where as PHP's MD5 returns a hex representation of the data
> (i.e. a 32-byte string).
>
> OpenSRS code is Perl, so it expects the binary hash. This makes a big
> difference when you then encode the string. :)
>
>
> --
> Colin Viebrock
> Co-Founder, easyDNS Technologies
> http://www.easyDNS.com/
>
>
