> From: openssl-users On Behalf Of Dr.
> Matthias St. Pierre
> Sent: Monday, 28 December, 2020 11:50
> I have no experience with zsh, but it seems that quoting is handled
> differently by zsh?
Is the problem that quoting is handled differently, or that he actually had
Unicode left-double-quote
> From: openssl-users On Behalf Of Jochen
> Bern
> Sent: Friday, 25 December, 2020 03:37
I believe David von Oheimb has already provided a solution for the original
problem in this thread (setting subjectKeyIdentifier and authorityKeyIdentifer
lets OpenSSL pick the right certificate from the tr
> From: openssl-users On Behalf Of Jochen
> Bern
> Sent: Friday, 25 December, 2020 03:37
I believe David von Oheimb has already provided a solution for the original
problem in this thread (setting subjectKeyIdentifier and authorityKeyIdentifer
lets OpenSSL pick the right certificate from the tr
This certificate is not the same one causing the error message in your
original email. The error message you provided earlier included
"serial=17702460327850242852" (or f5:ab:c5:e0:63:f5:73:24 in hex) but the
certificate you provided here has serial=16005263760024127372
(de:1e:1e:97:18:ab:c7:8c).
I have no experience with zsh, but it seems that quoting is handled differently
by zsh?
At least it looks like the double quotes ended up in the GET line and you
simply received
an HTTP 404 Not Found (which is the reason why your digest isn’t correct.)
HTH,
Matthias
> GET /source/openssl-“1.1.
This is my first post. OpenSSL is not my forte.
The code below returns an unexpected checksum value for openssl-1.1.1i..
Strangely, when the same code is run for a previous version, the correct
checksum value is returned. Here is what I’ve tried:
1. Downloaded the current SHA256 value for
