Shouldn't the deprecation notice that's printed also print the version it was
deprecated in?
- Matthew Lindner
On Mar 4, 2020, at 2:48 PM, Dr Paul Dale
mailto:paul.d...@oracle.com>> wrote:
EXTERNAL MAIL:
openssl-project-boun...@openssl.org<mailto:openssl-project-
That speed app was
deprecated I just found out in this email thread.)
- Matthew Lindner
> On Feb 21, 2020, at 12:14 PM, Matt Caswell wrote:
>
> EXTERNAL MAIL: openssl-project-boun...@openssl.org
>
>
> On 21/02/2020 19:45, Matthew Lindner wrote:
>> As a user I'm
g and will
point out interface deficiencies. 3.0.0 should not ship with deprecated code in
the apps (and 1.1.1 should stop using deprecated code in its apps).
- Matthew Lindner
> On Feb 21, 2020, at 12:06 AM, Kurt Roeckx wrote:
>
> EXTERNAL MAIL: openssl-project-boun...@openssl.org
&g
Hi I'm a developer that writes code that interfaces with OpenSSL. One
perspective I think that is missing that I haven't seen is that error
codes that point to the exact point in the OpenSSL code that caused an
issue are often needed to debug code that interfaces with OpenSSL.
Importantly because t
I notice that the OpenSSL 3.0.0 design page
https://www.openssl.org/docs/OpenSSL300Design.html still references
"CAVS testing" even though CAVS testing is shortly ending with the
release of ACVP testing. See:
https://csrc.nist.gov/Projects/Automated-Cryptographic-Validation-Testing
The new format i
Hello OpenSSL Team,
The issues and pull requests on github are largely getting ignored, I
know the team is busy on the new release but please spend some time on
these as well.
Thank you,
Matthew Lindner
