Quickly check the contents, and in CAfile_Baltimore_root,
the value of Basic Constraints: CA: TRUE, pathlen: 1
That can be one reason.
Yuting Chen
-Original Message-
From: jason.kubi...@wellsfargo.com via RT
Sent: Saturday, April 25, 2015 2:13 AM
Cc: openssl-dev@openssl.org
Subject: [op
Quickly check the contents, and in CAfile_Baltimore_root,
the value of Basic Constraints: CA: TRUE, pathlen: 1
That can be one reason.
Yuting Chen
-Original Message-
From: jason.kubi...@wellsfargo.com via RT
Sent: Saturday, April 25, 2015 2:13 AM
Cc: openssl-dev@openssl.org
Subject: [
Are the AKID(s) of the target certificates same as SKID(s) of the issuers?
As what I have observed and reported, OpenSSL cannot tackle such
kind of problems.
Yuting
-Original Message-
From: jason.kubi...@wellsfargo.com via RT
Sent: Saturday, April 25, 2015 2:13 AM
Cc: openssl-dev@openssl
Are the AKID(s) of the target certificates same as SKID(s) of the issuers?
As what I have observed and reported, OpenSSL cannot tackle such
kind of problems.
Yuting
-Original Message-
From: jason.kubi...@wellsfargo.com via RT
Sent: Saturday, April 25, 2015 2:13 AM
Cc: openssl-dev@opens
When I try to verify a SHA-2 certificate that chains up to a SHA-1 root I get
error 20 at depth 0. If I leave the SHA-1 root off of the CAfile I get past
depth 0. Verizon support was able to replicate this issue as well.
We are trying to use OpenSSL verify to check our intermediate issuing CA
(
Hello,
Summary: currently function LIBEAY32!OPENSSL_isservice() calls
USER32!GetDesktopWindow() to determine if the code is running as a service or
not. That function call is not necessary. Attached patch has the details.
Additional data:
1) Operating systems affected: all version of Windows.
