Re: CAPI engine seems to break server validation

2020-10-23 Thread Jakob Bohm via openssl-users
On 2020-10-23 15:45, Matt Caswell wrote: On 23/10/2020 14:10, Brett Stahlman wrote: It seems that the CAPI engine is breaking the server verification somehow. Note that the only reason I'm using the ca-bundle.crt is that I couldn't figure out how to get CAPI to load the Windows "ROOT"

Re: CAPI engine seems to break server validation

2020-10-23 Thread Matt Caswell
On 23/10/2020 14:10, Brett Stahlman wrote: > It seems that the CAPI engine is breaking the server verification somehow. > Note that the only reason I'm using the ca-bundle.crt is that I couldn't > figure out how to get CAPI to load the Windows "ROOT" certificate > store, which contains the

CAPI engine seems to break server validation

2020-10-23 Thread Brett Stahlman
Hello, I'm attempting to use the s_client command on Windows 10 to connect to a secure server (client.badssl.com) that requires client authentication. When I run the following command... echo -e 'GET / HTTP/1.1\r\nHost: client.badssl.com\r\n\r\n' | ./dist/bin/openssl.exe s_client -ign_eof

Re: alternative for x509 "name" field

2020-10-23 Thread Tomas Mraz
On Fri, 2020-10-23 at 14:39 +0530, shiva kumar wrote: > Hi, > > Compared to OpenSSL 1.0.2 and 1.1.0 and above, in struct > x509_st , char *name field has been removed, what is the alternative > for it and what is the impact? can anyone please answer the query? Hi, although the name field was

alternative for x509 "name" field

2020-10-23 Thread shiva kumar
Hi, Compared to OpenSSL 1.0.2 and 1.1.0 and above, in struct x509_st , char *name field has been removed, what is the alternative for it and what is the impact? can anyone please answer the query? Thanks and regards Shivakumar