.
Regards,
Dingping
David von Oheimb 于2021年1月2日周六 上午5:17写道：
> On 01.01.21 08:07, 定平袁 wrote:
>
> @David von Oheimb
> Thank you so much for your deep investigation!
>
> My pleasure!
>
> With subjectKeyIdentifier and authorityKeyIdentifier extensions, it works
> lik
@Jochen Bern
Thanks for your reply!
I didn't describe the problem clearly due to lack of tls domain knowledge.
Now I know my cert is self-signed end entity cert, and the statement I
found
on openssl website does not apply to me. The behavior is similar(Actually
not the same,
since my two certs ha
up the right cert, do you think
OpenSSL
will implement this logic too? Or it's a more appropriate approach to just
use the extensions you suggested?
Regards,
Dingping
David von Oheimb 于2020年12月26日周六 下午5:17写道：
> On 25.12.20 00:35, 定平袁 wrote:
>
> @David von Oheimb I will update to a
icate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
Is above information enou
Thanks a lot for your reply! Merry Christmas!
@Michael WojcikApologies. I clicked the
wrong reply button.
@David von Oheimb I will update to a new version and try
again. To append cert is to make sure new cert and old cert both exist in
trust store, thus when server switches cert, it can be
parameters will be searched?
定平袁 于2020年12月20日周日 上午8:59写道：
> Hello everyone,
>
> Recently I am trying to rotate a cert, and the client uses python requests
> lib, which leverages openssl. Here is my steps:
>
> 1. Generate a new cert, and append it to the cert file(at this point,
>
Hello everyone,
Recently I am trying to rotate a cert, and the client uses python requests
lib, which leverages openssl. Here is my steps:
1. Generate a new cert, and append it to the cert file(at this point, there
are 2 certs in the file, first is old cert, second is new, they have the
same Subj
