[openssl-dev] [openssl.org #4697] Bug in 1.1.0 (lost compatibility with previous releases)

[David Woodhouse]

On Wed, 2016-10-05 at 07:17 +0000, Viktor Dukhovni wrote:
> On Wed, Oct 05, 2016 at 07:05:06AM +0000, Sergey G Brazhnikov via RT wrote:
> 
> > 
> > Just figured out that files encrypted with OpenSSL 1.1.0-stable can not be
> > decrypted with previous releases and vice versa.
> > Tested aes256, cast5-cfb, camellia128 on 1.1.0-stable, 1.0.2-stable and
> > 0.9.8(cast5-cfb only)
> > 
> > All built without errors, passed all tests.
> > Configuration VC-WIN32, os Windows 8.1 Pro x64, compiler vs2015.
> 
> Especially on Windows systems you have to be mindful of the
> character-set encoding of the passphrase.
> 
> Try setting OPENSSL_WIN32_UTF8=1 in your environment and see if
> that helps.  For interoperable password-based encryption the password
> character-set needs to be standard.

Wait a minute.

Yes, the character-set needs to be standard. It is a bug in OpenSSL
that we don't convert from the locale character set *to* something
standard, before key derivation.

And the *only* justification for the fact that bug continues to exist —
and in fact we introduced a *new* bug in OpenSSL 1.1 instead of fixing
it — is for backward compatibility with older releases.

So how can we be so sanguine about the above failure report?

-- 
dwmw2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5760 bytes
Desc: not available
URL: <http://mta.openssl.org/pipermail/openssl-dev/attachments/20161005/e5bc54ac/attachment-0001.bin>