Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

certificate expired #1562

Open
chenzl-123 opened this issue Jan 15, 2025 · 0 comments
Open

certificate expired #1562

chenzl-123 opened this issue Jan 15, 2025 · 0 comments

Comments

@chenzl-123
Copy link

Trace : 4, 20250115 150242.290 SSL cipher available: 53:RSA-PSK-AES128-CBC-SHA256
Trace : 4, 20250115 150242.290 SSL cipher available: 54:DHE-PSK-AES128-CBC-SHA256
Trace : 4, 20250115 150242.290 SSL cipher available: 55:RSA-PSK-AES128-CBC-SHA
Trace : 4, 20250115 150242.290 SSL cipher available: 56:DHE-PSK-AES128-CBC-SHA
Trace : 4, 20250115 150242.290 SSL cipher available: 57:AES128-SHA
Trace : 4, 20250115 150242.290 SSL cipher available: 58:PSK-AES128-CBC-SHA256
Trace : 4, 20250115 150242.290 SSL cipher available: 59:PSK-AES128-CBC-SHA
Trace : 4, 20250115 150242.290 SSL handshake started write:unknown:unknown
Trace : 4, 20250115 150242.290 SSL state connect:before SSL initialization:(NONE)
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write client hello:(NONE)
Trace : 4, 20250115 150242.290 SSL connect:SSLv3/TLS write client hello
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write client hello:(NONE)
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS read server hello:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:TLSv1.3 read encrypted extensions:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS read server certificate request:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS read server certificate:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:TLSv1.3 read server certificate verify:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS read finished:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write change cipher spec:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write client certificate:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write certificate verify:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL state connect:SSLv3/TLS write finished:TLS_AES_256_GCM_SHA384
Trace : 4, 20250115 150242.290 SSL handshake done write:unknown:unknown
Trace : 4, 20250115 150242.379 SSL certificate verification: X509_V_OK
Trace : 4, 20250115 150242.379 SSL connect:SSL negotiation finished successfully
Trace : 4, 20250115 150242.379 3 paho-c-pub -> CONNECT version 4 clean: 1 (0)
Trace : 4, 20250115 150242.379 SSL alert read:fatal:certificate expired
Trace : 4, 20250115 150242.379 Connecting to serverURI 114.116.96.214:9883 with MQTT version 3

Can a clear result be returned when using an expired certificate to connect to the server?
From the SSL log, it can be seen that 'SSL certificate verification: X509_V'OK', but 'SSL alert read: fatal: certificate expired'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant