News for hackers. Stuff that matters.
Re:OpenSSL 1.1 API migration path, or the lack thereof by rurban on Friday December 30, 2016 @11:02AM (#13284968)
Contrary to the op's subject I can easily see the benefit of the API changes in the new major version, and I see good documentation of the API migration path: https://wiki.openssl.org/index.php/1.1_API_Changes

It will need some time to port all these projects over to 1.1 but everyone can easily see the benefits. Supporting both will be a nightmare. Just drop 1.0 support and require 1.1

Re:OpenSSL 1.1 API migration path, or the lack thereof by gbrown_ on Friday December 30, 2016 @11:18AM (#13285084)
> Just drop 1.0 support and require 1.1

The point is applications won't be able to easily do this. As the post points out it's likely many distributions will adopt the 1.0 release series due to the length of support. So if you only use to 1.1 API you may find the burden of installing another OpenSSL release is placed on your users as their base system contains a version of OpenSSL with an incompatible API.

To be clear I think the API change has good intention but it would be been nicer to have marked parts depreciated and introduced new interfaces more gradually. OpenSSH is a good example of this in terms of advertising ahead of time breaking changes.

Re:OpenSSL 1.1 API migration path, or the lack thereof by aomix on Friday December 30, 2016 @11:22AM (#13285126)
But that is nearly a two sentence summary of the post.

  -The API changes are needed and good
  -The migration to 1.1 will be difficult
The argument is just that it's not realistic for many OpenSSL users to drop 1.0 for a variety of reasons.