6

We use OpenSSL on a CentOS 6 server to monitor the certificate on servers for RDP.

To do this we use:

openssl s_client -connect SERVER01:3389 -prexit

This has worked flawlessly until 4 days ago, when it suddenly stops showing that a cert is used and instead shows the following for a single server:

CONNECTED(00000003)
140439032170136:error:140790E5:SSL routines:ssl23_write:ssl handshake failure:s23_lib.c:177:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 305 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time: 1539710511
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 0 bytes and written 305 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time: 1539710511
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

I have seen that older versions of OpenSSL caused this error, but since the version hasn't change (1.0.1e) and it was working, I cannot see what is wrong.

I've also tried resetting the server's RDP cert, but again no change.

10
  • So RDP TLS connections are working, the issue is the OpenSSL test is failing?
    – Greg Askew
    Oct 16, 2018 at 19:30
  • That is correct. Suddenly after years of working, is stopped for this one server. Others work as per normal. The openssl server can access it so it's not firewall, and I have tested from other systems and get same result. Oct 16, 2018 at 20:32
  • I ran into the same issue a few days ago. Was nobody able to come up with a solution?
    – Daywalker
    Apr 29, 2021 at 7:01
  • 1
    It sounds your RDP isn't listening over SSL anymore. I think you're looking to openssl, but the problem is at the RDP side May 3, 2021 at 17:53
  • 1
    I'd check cipher suite or TLS version default changes between 18.04 and 20.04. The newer OS might default to a more secure set that doesn't have any matches with what is enabled on the Windows server. You might also be able to see the mismatch in a packet capture during the TLS handshake. May 5, 2021 at 16:25

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.