Re: full-chain ocsp stapling

2019-10-10 Thread Jeremy Harris
On 01/10/2019 12:21, Jeremy Harris wrote: > I'm using the indexfile variant. It seems that the -CA argument > needs to be the signer of the cert, not the CA for the chain; and > you cannot give -CA multiple times. So you don't get good OCSP status > for all elements in the chain: > $ openssl

Re: FIPS 3.0 private_* hash functions

2019-10-10 Thread Tomas Mraz
On Thu, 2019-10-10 at 08:40 -0700, Neptune wrote: > Hi all, > I am in the process of making required changes to migrate our code to > the > 1.1.x branch. We are currently using the FIPS Object Module 2.0 and > eagerly > await word on the new 3.0 FIPS Object Module, but in the meantime > there is >

Re: FIPS 3.0 private_* hash functions

2019-10-10 Thread Matt Caswell
On 10/10/2019 16:40, Neptune wrote: > Hi all, > I am in the process of making required changes to migrate our code to the > 1.1.x branch. We are currently using the FIPS Object Module 2.0 and eagerly > await word on the new 3.0 FIPS Object Module, but in the meantime there is > one issue of

FIPS 3.0 private_* hash functions

2019-10-10 Thread Neptune
Hi all, I am in the process of making required changes to migrate our code to the 1.1.x branch. We are currently using the FIPS Object Module 2.0 and eagerly await word on the new 3.0 FIPS Object Module, but in the meantime there is one issue of concern in our code for which I need some

Openssl config file string_mask

2019-10-10 Thread Richard Olsen
On our RHEL7 system I created a local CA. When i try to sign the linux created csr there is no problem. But trying to sign from Palo Alto or F5 csr's it errors with The stateOrProvinceName field needed to be the same > in the CA certificate CA certificate (My Entry) and the request (My Entry)

AW: AW: building OpenSSL 1.1.1 with -DPURIFY

2019-10-10 Thread Dr. Matthias St. Pierre
> > The easiest way to obtain the fix is to update to the current head of the > > 1.1.1. stable branch. > > https://github.com/openssl/openssl/commits/OpenSSL_1_0_1-stable > > I think you meant to link to the 1.1.1 branch not 1.0.1! > >

RE: building OpenSSL 1.1.1 with -DPURIFY

2019-10-10 Thread tim.j.culhane
Hi all, Glad to report that using the latest 1.1.1 stable build from git, all tests pass successfully and also my issue with the valgrind issues is resolved. Many thanks for your prompt help. Tim -Original Message- From: Dr. Matthias St. Pierre Sent: Wednesday 9 October 2019 22:58

Re: AW: building OpenSSL 1.1.1 with -DPURIFY

2019-10-10 Thread Matt Caswell
On 09/10/2019 22:57, Dr. Matthias St. Pierre wrote: > Hi Tim, > >> However, when I run the tests there appears to be failures. >> >> Extract of the make test output below: >> >> >> ../test/recipes/20-test_enc.t .. >> Dubious, test returned 1 (wstat 256, 0x100) >> Failed