That hex key string looks off. It seems to include an ending \n (0a), which I
suspect is because at an earlier time, someone forgot to peal off the ending
linefeed. Take away the endine 0a and I'm sure things will be fine.
The 'set_hex' check is exactly the same in the 1.0.1, 1.0.2 and upcoming
As I said, I think there was a bug in previous versions that got the 'too long'
check wrong. The command line that you posted is in error. There are two extra
characters. As the message says :)
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4552
Please log in as guest with password
ich via RT [mailto:r...@openssl.org]
Sent: Tuesday, May 31, 2016 4:45 PM
To: David-E Young
Cc: openssl-dev@openssl.org
Subject: RE: [openssl-dev] [openssl.org #4552] Bug report: hex string is too
long, problem in set_hex()?
> If the size multiplier is changed to, say, 4, then the proble
> If the size multiplier is changed to, say, 4, then the problem goes away with
> no apparent ill effects. Reading the code for set_hex() and its caller, it
> does
> not appear that the size multiplier is related to a buffer size or some other
> limitation.
Yes it is, it's the size of the buffer
Classification: Public
OS: SUSE Linux Enterprise Server 11 SP2 (x86_64)
OpenSSL: versions 1.0.1m, 1.1.0-pre5
Using this command sequence:
echo WuNhPwuWAOiG86RfO4A5jITR9WZ+kF1L+iBgGPQJ4dEJk8Sxiqb014bJsEGDbCfk |
$ssl/bin/openssl enc -aes128 -d -a -iv 57fd56a7e47b9482096ab4707ca9d383 -K
