Re: [openssl-dev] procedure for adding new engine registration

2015-12-08 Thread Vemulapalli Jyothi
Hi Matt, We could successfully execute dynamic engine support. Thanks for help. One issue regarding cleanup. When I gone through openssl cleanup (ie apps_shutdown() or engine interface cleanup ) functionality, I see that there are two function pointers that can set to ENGINE interface: destroy

[openssl-dev] Openssl 1.0.2e is compatible with FIPS module openssl-fips-2.0.10

2015-12-08 Thread Patil, Ashwini IN BLR SHC
Hello All, Please let me know if the Openssl 1.0.2e is compatible with FIPS module openssl-fips-2.0.10. Your help is appreciated. With best regards, Ashwini V Patil Siemens Healthcare Private Limited HC SI DC IN H1-FH STD IBP 6 84, Hosur Road Bengaluru 560100, Indien Mobil: +91 9008132565 mailt

Re: [openssl-dev] [openssl-team] Discussion: design issue: async and -lpthread

2015-12-08 Thread Paul Dale
The "have-atomics" is intended to test if the callback was installed by the user. If we're using an atomic library or compiler support, then it isn't required since we know we've got them. Likewise, the lock argument isn't required if atomics are used everywhere. However, some code will need

Re: [openssl-dev] [openssl-team] Discussion: design issue: async and -lpthread

2015-12-08 Thread Nico Williams
On Wed, Dec 09, 2015 at 09:27:16AM +1000, Paul Dale wrote: > It will be possible to support atomics in such a way that there is no > performance penalty for machines without them or for single threaded > operation. My sketcy design is along the lines of adding a new API > CRYPTO_add_atomic that ta

Re: [openssl-dev] [openssl-team] Discussion: design issue: async and -lpthread

2015-12-08 Thread Paul Dale
It will be possible to support atomics in such a way that there is no performance penalty for machines without them or for single threaded operation. My sketcy design is along the lines of adding a new API CRYPTO_add_atomic that takes the same arguments as CRYPTO_add (i.e. reference to counter, v

Re: [openssl-dev] [openssl-team] Discussion: design issue: async and -lpthread

2015-12-08 Thread Nico Williams
On Tue, Dec 08, 2015 at 11:19:32AM +0100, Florian Weimer wrote: > > Maybe http://trac.mpich.org/projects/openpa/ would fit the bill? > > It seems to have trouble to keep up with new architectures. New architectures are not really a problem because between a) decent compilers with C11 and/or non-C

Re: [openssl-dev] [openssl.org #4175] Add new macro or PKCS7 flag to disable the check for both data and content

2015-12-08 Thread Long, Qin via RT
Agree. It will be more straight to remove the if() test here, since the later logic will handle the inData directly if this parameter was provided. > -Original Message- > From: Salz, Rich via RT [mailto:r...@openssl.org] > Sent: Tuesday, December 8, 2015 8:56 PM > To: Long, Qin > Cc: ope

Re: [openssl-dev] [openssl.org #4156] Wrong expectation of value of _IOB_ENTRIES with Visual Studio 2015

2015-12-08 Thread Hannes Mezger via RT
Hi, thanks for the detailed explanation. We can change our code to use the BIO-functionality instead of using FILE pointers, so far this works fine and even simplifies our code. But two issues remain: 1. There is still no explanation on why it worked fine with Visual Studio 2005 - 2013 (yes, che

Re: [openssl-dev] [openssl.org #4175] Add new macro or PKCS7 flag to disable the check for both data and content

2015-12-08 Thread Salz, Rich via RT
I think that instead of the #ifdef being removed, the if() test should be removed. This was my mistake. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] [openssl.org #4175] Add new macro or PKCS7 flag to disable the check for both data and content

2015-12-08 Thread Long, Qin via RT
The OpenSSL new release / HEAD updates removed the following comment-out statement in PKCS7_verify() routine, which will return error for one call if both embedded-content and detached data were provided. #if 0 --> Removed /* * NB: this test commented out because some versions of

Re: [openssl-dev] [openssl-team] Discussion: design issue: async and -lpthread

2015-12-08 Thread Florian Weimer
* Nico Williams: > Maybe http://trac.mpich.org/projects/openpa/ would fit the bill? It seems to have trouble to keep up with new architectures. ___ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev