![]() With the certificate configured I still weren’t able to connect. The following article was helpful in getting the certificate installed: I then generate my own csr using OpenSSL and got myself a SHA-256 signature algorithm certificate. This should have been a good hint as to why I wasn’t able to establish a trusted connection later. My CA did not like the csr as it was SHA-1, and my CA will only issue SHA-256 leafs. I try to generate the csr on the ASA: crypto ca enroll SSL-Trustpoint So, it’s not liking the self signed SSL certificate anymore, fair enough, that’s just been laziness on my part, so lets get a proper cert from the CA. Looking at the application logging I see that it’s failing with the following trace: : Received fatal alert: handshake_failureĪt .getSSLException(Alerts.java:192)Īt .getSSLException(Alerts.java:154)Īt .recvAlert(SSLSocketImpl.java:2023)Īt .readRecord(SSLSocketImpl.java:1125)Īt .performInitialHandshake(SSLSocketImpl.java:1375)Īt .startHandshake(SSLSocketImpl.java:1403)Īt .startHandshake(SSLSocketImpl.java:1387) When trying to access it using the ASDM I got the following unhelpful error message: “Unable to launch device manager from ”. After updating Cisco ASA 5505 to software version 9.2(4) and ASDM 7.6(2)150 I found myself unable to manage it using ASDM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |