Deprecation

[Dr Paul Dale]

There is some pushback against the deprecations going on in various PRs.

The plan has always been to deprecate engines in 3.0 and removing support for them 5+ years later.  Originally, the path was to have included an engine provider that could load engines and make them appear to be a provider.  After a fair amount of investigation, this was deemed to be too difficult in the 3.0 time frame.

Do we still want to deprecate engines in 3.0?
Should we defer until 4.0 instead?


The main benefits seem to boil down to continuing to support existing engines vs removing the legacy code paths and switching to the provider model.


Pauli
-- 
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations 
Phone +61 7 3031 7217
Oracle Australia

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-project/attachments/20200214/04d39701/attachment.html>