On 9 January 2016 at 22:45, Salz, Rich wrote:
>
> > required to perform many operations. What do people think about
> > backporting those accessors into the 1.0.2 branch?
>
> Another possibility is to have a just a single (new) header file that has
> #define's for the accessors that turn into raw
On Sat, Jan 09, 2016, Paul Kehrer wrote:
> The ASN1 functions for NAME_CONSTRAINTS are not declared or implemented in
> the current OpenSSL releases. This is inconsistent with other extension
> structs and (I believe) means you either need to declare them yourself or
> attempt to build NAME_CON
You might also take a look at https://rt.openssl.org/Ticket/Display.html?id=3502
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
> -Original Message-
> From: Paul Kehrer [mailto:paul.l.keh...@gmail.com]
> Sent: Saturday, January 09, 2016 3:20 PM
> To:
> required to perform many operations. What do people think about
> backporting those accessors into the 1.0.2 branch?
Another possibility is to have a just a single (new) header file that has
#define's for the accessors that turn into raw structure access.
__
> Any idea when these will be in github?
Hopefully in time for the next alpha 1.1 release, in a week or two.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
> Any idea when these will be in github?
Hopefully in time for the next alpha 1.1 release, in a week or two.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
With OpenSSL 1.1.0 opaquing most of the structs getter/setter functions are
required to perform many operations. What do people think about backporting
those accessors into the 1.0.2 branch? It might simplify supporting 1.1.0 (but
only as projects drop 0.9.8/1.0.0/1.0.1 support of course).
-Pau
The ASN1 functions for NAME_CONSTRAINTS are not declared or implemented in the
current OpenSSL releases. This is inconsistent with other extension structs and
(I believe) means you either need to declare them yourself or attempt to build
NAME_CONSTRAINTS using nconf functions. Below is a patch t
Thanks, Roumen's patches looks good and also include EC_KEY_set_method to
replace the working ECDSA_set_method and ECDH_set_method in 1.0.2.
Any idea when these will be in github?
On 1/8/2016 11:30 AM, Salz, Rich via RT wrote:
> There is a fix for this that is in the internal code-review phas
Thanks, Roumen's patches looks good and also include EC_KEY_set_method to
replace the working ECDSA_set_method and ECDH_set_method in 1.0.2.
Any idea when these will be in github?
On 1/8/2016 11:30 AM, Salz, Rich via RT wrote:
There is a fix for this that is in the internal code-review phas
anuary 09, 2016 8:55 AM
> To: openssl-dev@openssl.org; openssl-us...@openssl.org
> Subject: [openssl-users] openssl-SNAP-20160109 issue
>
> In a amke && make test
>
> I got
>
> making all in engines/ccgost...
> gcc -I.. -I../include -I../crypto/include -I../fips
> SSLKEYLOGFILE env var is a good current standard, so I think openssl should
> use it as well.
Patches to implement all of this would be helpful, otherwise it will probably
not make it into the next relese.
___
openssl-dev mailing list
To unsubscrib
In a amke && make test
I got
making all in engines/ccgost...
gcc -I.. -I../include -I../crypto/include -I../fips -fPIC -DOPENSSL_PIC
-DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -DPERL5 -DL_ENDIAN -DTERMIOS -fomit-frame-pointer
-O2 -mar
This implementation is not enough, beacuse it works only for openssl
s_client app. However it should work for all apps using openssl as a
library (eg. curl, nginx).
SSLKEYLOGFILE env var is a good current standard, so I think openssl should
use it as well.
Regards,
Jan Zak
On Tue, Dec 29, 2015
14 matches
Mail list logo
