I think Jakob’s real concern (as expressed to me off-list a month or so ago) is
that OpenSSL’s libcrypto will become entirely hidden. I found several of his
comments confusing until he mentioned that. So, I think the fair question to
be asking is:
Is there any plan to make libcrypto go
Is there any plan to make libcrypto go completely opaque, such that _only_
the APIs exposed in libssl will be available?
Absolutely not.
Thanks for asking!
___
openssl-users mailing list
To unsubscribe:
On 10/02/15 21:16, Tom Francis wrote:
I think Jakob’s real concern (as expressed to me off-list a month or so ago)
is that OpenSSL’s libcrypto will become entirely hidden. I found several of
his comments confusing until he mentioned that. So, I think the fair
question to be asking is:
On 07/02/2015 12:12, Michael Felt wrote:
From someone who does NOT understand the in's and out's of what people
(developers and users) have been using openSSL for.
My first reaction is: have developers been using openSSL, or has it
gone to abusing it?
For the sake of argument - let's say just
From someone who does NOT understand the in's and out's of what people
(developers and users) have been using openSSL for.
My first reaction is: have developers been using openSSL, or has it gone to
abusing it?
For the sake of argument - let's say just use as it has always been
intended.
Many
On 05/02/2015 00:42, Salz, Rich wrote:
Not much on that page so far, not even a kill list of
intended victims except an admission that EAY's popular DES
library can no longer be accessed via the copy in OpenSSL.
Yup. Pretty empty. Over the coming year there will be more.
I fear that this is
Thanks for your detailed reply. Not sure what else I can say except that we
disagree.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On 06/02/15 16:03, Jakob Bohm wrote:
I believe you have made the mistake of discussing only amongst
yourselves, thus gradually convincing each other of the
righteousness of a flawed decision.
...and, Rich said in a previous email (in response to your comment):
I fear that this is an
On 03/02/2015 23:02, Rich Salz wrote:
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
Not much on that page so far, not even a kill list of
intended victims except an admission that EAY's popular DES
library can no longer be accessed via the copy in OpenSSL.
Yup. Pretty empty. Over the coming year there will be more.
I fear that this is an indication that you will be killing
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
11 matches
Mail list logo
