<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 03/02/2015 23:02, Rich Salz wrote:<br>
</div>
<blockquote cite="mid:20150203220231.GA12587@openssl.org"
type="cite">
<pre wrap="">As we've already said, we are moving to making most OpenSSL data
structures opaque. We deliberately used a non-specific term. :)
As of Matt's commit of the other day, this is starting to happen
now. We know this will inconvenience people as some applications
no longer build. We want to work with maintainers to help them
migrate, as we head down this path.
We have a wiki page to discuss this effort. It will eventually include
tips on migration, application and code updates, and anything else the
community finds useful. Please visit:
<a class="moz-txt-link-freetext" href="http://wiki.openssl.org/index.php/1.1_API_Changes">http://wiki.openssl.org/index.php/1.1_API_Changes</a>
Thanks.
_______________________________________________
openssl-users mailing list
To unsubscribe: <a class="moz-txt-link-freetext" href="https://mta.openssl.org/mailman/listinfo/openssl-users">https://mta.openssl.org/mailman/listinfo/openssl-users</a>
</pre>
</blockquote>
<tt>Not much on that page so far, not even a "kill list" of<br>
intended victims except an</tt><tt> </tt><tt>admission that EAY's
popular DES<br>
library can no longer be accessed via the copy</tt><tt> </tt><tt>in
OpenSSL.</tt><br>
<br>
<tt>I fear that this is an indication that you will be killing<br>
off all the other</tt><tt> </tt><tt>non-EVP entrypoints in
libcrypto, making<br>
it much harder to use the</tt><tt> </tt><tt>library with
experimental or<br>
non-standard algorithms and methods.</tt><tt><br>
<br>
Just consider how hard it would now be to use libcrypto to<br>
implement stuff like AES-GCM (if it was not already in the<br>
library) or any of the block modes that were proposed in<br>
the FIPS process, but not standardised by NIST (and thus<br>
not included in EVP).<br>
<br>
With the classic non-EVP API, it is trivial to wrap a custom<br>
mode around the basic DES/AES/IDEA/... block functions.<br>
<br>
And this is just one example of the flexibility provided by<br>
not going through the more rigid EVP API.<br>
</tt><br>
<tt>Should everyone not doing just TLS1.2 move to a different<br>
library</tt><tt> </tt><tt>now, such as crypto++ ?</tt><tt><br>
<br>
</tt>
<pre class="moz-signature" cols="72">Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. <a class="moz-txt-link-freetext" href="http://www.wisemo.com">http://www.wisemo.com</a>
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded </pre>
</body>
</html>