On an AlmaLinux 8.6 VM hosted in Proxmox:
[root@certs ~]# openssl verify -CAfile
/etc/ssl/certs/local/DOMAIN.wildcards.pem
/etc/ssl/certs/local/DOMAIN.wildcards.pem
C = US, O = Let's Encrypt, CN = R3
error 2 at 1 depth lookup: unable to get issuer certificate
error
On Fri, 2022-09-02 at 00:22 +, Wall, Stephen wrote:
> > A compromised server could easily still request the client
> > certificate, no?
> > But as noted, even a compromised server can ask for client
> > credentials and then
>
> Yes, that's true. If the intruder knew to do so. Also, a thief
On Fri, Sep 02, 2022 at 07:23:41AM +, Sethuraman Venugopal wrote:
> The SSL session is getting created successfully, but the session ID is
> coming as NULL, due to which the handshake is failing between the
> client and server.
Successful handshakes need not issue a non-empty session id.
> From: openssl-users On Behalf Of Viktor
> Dukhovni
>
> Of course this test should only be applied for a full handshake, reused
> sessions
> piggyback on the certificates exchanged in the original full handshake.
Thank you, that helps. I have not enabled session cache, so that's not a
Dear All,
In our project below are the openssl and TLS version we are consuming it
OpenSSL Version : OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
TLS Version : 1.2
Message Digest : SHA256
The SSL session is getting created successfully, but the session ID is coming
as NULL,
