[openssl-dev] 1.1 release being delayed

[Dr. Matthias St. Pierre]

> > And as far as regressions after beta 2 release are concerned, it looks
> > like there was a change in the API that is not backwards compatible. I
> > was hoping this would not happen after the "Beta 2 - Opaque work
> > complete". Did I misunderstand what that note means?
> >
> > The non-compatible change (this actually broke wpa_supplicant build..)
> > is this one:
> >
> > commit fd809cfdbd6e32b6b67b68c59f6d55fbed7a9327
> >     Constify the parameter getters for RSA, DSA and DH
> >
> > -void DH_get0_key(const DH *dh, BIGNUM **pub_key, BIGNUM **priv_key)
> > +void DH_get0_key(const DH *dh, const BIGNUM **pub_key, const BIGNUM **priv_key)
> >
> >
> > Is there a clear point in time after which the OpenSSL 1.1.0 API is
> > expected to be fully frozen for the release (well, other than the final
> > public release showing up)?
> >
> 
> We are not planning any more opaque work before release, and are trying
> to avoid API breaks at this late stage - but we can't fully rule it out
> either.
> 
> Matt


+1 for the change. IMHO, the constification is a bug fix of the api, not a
deliberate change. Having a const-incorrect api is always a nuisance and it
is better to have it fixed now than after the final elease.

Matthias

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