Re: OpenSSL and Crypt::CBC don't give the same ciphertext

UPDATE: I fixed it .... It should have been H* instead of h* in my pack statements

On my Windows machine I find that it does indeed need to be "H*".
I also need to binmode $pipe if I want test.bin and cryptx.bin to agree.
The contents of those 2 files will change (but still be in agreement) depending upon whether I binmode $infile.
The binmode $infile therefore apparently affects what is fed in - but, as you observed, both ciphers will receive identical inputs in any case.

I think (untested) you might be able to avoid the binmode calls if you're not on Windows.

Cheers,
Rob

Comment on Re: OpenSSL and Crypt::CBC don't give the same ciphertext Select or Download Code

Replies are listed 'Best First'.
Re^2: OpenSSL and Crypt::CBC don't give the same ciphertext (binmode always) by Anonymous Monk on Feb 06, 2016 at 04:10 UTC
syphilis : I think (untested) you might be able to avoid the binmode calls if you're not on Windows. :D how many thousands of times have you seen the solution to a problem was a missing call to binmode? binmode on linux, binmode on windows, binmode always :D	[reply]
Re^3: OpenSSL and Crypt::CBC don't give the same ciphertext (binmode always) by syphilis (Archbishop) on Feb 06, 2016 at 06:05 UTC
how many thousands of times have you seen the solution to a problem was a missing call to binmode? I've seen that lots of times .... on Windows ;-) Cheers, Rob	[reply]
Re^4: OpenSSL and Crypt::CBC don't give the same ciphertext (binmode always) by LonelyPilgrim (Beadle) on Feb 09, 2016 at 23:01 UTC
The binmode can't hurt, and makes the code more portable. It makes explicit that this is binary data we are dealing with and we don't want anybody monkeying with our bytes. I do run Perl on Windows machines pretty often, and I have no expectation that whomever I send a script to will be running *nix. If I remember to do this beforehand, I don't have to beat my head against it later wondering why it doesn't work. :)	[reply]