Java:使用自签名证书的SSL客户端身份验证
Java:使用自签名证书的SSL客户端身份验证
提问于 2010-12-12 20:07:37
我正在尝试保护来自通过Internet进行通信的Java客户机/服务器应用程序的连接。我的想法是将SSL套接字与自签名证书和客户端身份验证结合使用。我做了以下工作：
- 服务器:包含新的自签名证书的密钥库。包含新的自签名证书的
keytool -genkey -kelalg RSA ... - Client:密钥库。包含导出的客户端证书的
keytool -genkey -kelalg RSA ... - Server:信任库(来自上面的项目符号)。用于导出客户端证书的
keytool -export和用于将其导入到包含导出的服务器证书的服务器的truststore - Client:信任库中的
keytool -import -v -trustcacerts(从第一个项目符号开始)。keytool -export用于导出服务器证书，keytool -import -v -trustcacerts用于将其导入客户端的信任库
信任库和密钥库已正确连接到服务器/客户端。我可以看到正在加载的证书(SSL调试信息)。但整件事都不管用。在SSL握手期间，我得到以下错误(SSL调试信息)：
main, WRITE: TLSv1 Handshake, length = 897
main, READ: TLSv1 Handshake, length = 141
*** Certificate chain
***
main, SEND TLSv1 ALERT: fatal, description = bad_certificate
main, WRITE: TLSv1 Alert, length = 2
main, called closeSocket()
main, handling exception: javax.net.ssl.SSLHandshakeException: null cert chain
main, IOException in getSession(): javax.net.ssl.SSLHandshakeException: null cert chain
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(Unknown Source)
at sslsocket.Server.getClientDistinguishedName(Server.java:86)
at sslsocket.Server.main(Server.java:37)当我禁用客户端身份验证时，它可以完美地工作。
如果能帮上忙我会很感激的。非常感谢!
下面是来自服务器的完整的匿名输出：
Initializing SSL
***
found key for : server
chain [0] = [
[
Version: V3
Subject: CN=xxxxxx Server, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 9487726xxxxxx15617628447913191
public exponent: 65537
Validity: [From: Thu Dec 09 17:04:05 CET 2010,
To: Wed Jul 03 18:04:05 CEST 2109]
Issuer: CN=xxxxxx Server, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
SerialNumber: [ 4dxxxxxx5]
]
Algorithm: [SHA1withRSA]
Signature:
0000: 6F 06 1D EA E9 DC 5B 5D EC EB 33 D4 47 01 94 1A o.....[]..3.G...
xxxxxx
0070: 99 78 C4 31 5F 84 8F 7B C1 2F 10 A1 9F 50 72 A1 .x.1_..../...Pr.
]
***
adding as trusted cert:
Subject: CN=xxxxxx Client, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
Issuer: CN=xxxxxx Client, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
Algorithm: RSA; Serial number: 0x4xxxxxx0
Valid from Thu Dec 09 17:06:56 CET 2010 until Wed Jul 03 18:06:56 CEST 2109
trigger seeding of SecureRandom
done seeding SecureRandom
Opening socket
Waiting for clients...
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
matching alias: server
main, called closeSocket()
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
[read] MD5 and SHA1 hashes: len = 3
0000: 01 03 01 ...
[read] MD5 and SHA1 hashes: len = 98
0000: 00 3C 00 00 00 20 00 00 04 01 00 80 00 00 05 00 .<... ..........
xxxxxx
0060: 26 51 &Q
main, READ: SSL v2, contentType = Handshake, translated length = 75
*** ClientHello, TLSv1
RandomCookie: GMT: 1292088238 bytes = { 223,xxxxxx, 81 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression Methods: { 0 }
***
%% Created: [Session-1, SSL_RSA_WITH_RC4_128_MD5]
*** ServerHello, TLSv1
RandomCookie: GMT: 1292088238 bytes = { 222,xxxxxx, 241 }
Session ID: {77,xxxxxx, 235}
Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
Compression Method: 0
Extension renegotiation_info, renegotiated_connection: <empty>
***
Cipher suite: SSL_RSA_WITH_RC4_128_MD5
*** Certificate chain
chain [0] = [
[
Version: V3
Subject: CN=xxxxxx Server, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5
Key: Sun RSA public key, 1024 bits
modulus: 948772xxxxxx17628447913191
public exponent: 65537
Validity: [From: Thu Dec 09 17:04:05 CET 2010,
To: Wed Jul 03 18:04:05 CEST 2109]
Issuer: CN=xxxxxx Server, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH
SerialNumber: [ 4d00fdf5]
]
Algorithm: [SHA1withRSA]
Signature:
0000: 6F 06 1D EA E9 DC 5B 5D EC EB 33 D4 47 01 94 1A o.....[]..3.G...
xxxxxx
0070: 99 78 C4 31 5F 84 8F 7B C1 2F 10 A1 9F 50 72 A1 .x.1_..../...Pr.
]
***
*** CertificateRequest
Cert Types: RSA, DSS
Cert Authorities:
<CN=xxxxxx Client, OU=communication, O=xxxxxx, L=Zuerich, ST=ZH, C=CH>
*** ServerHelloDone
[write] MD5 and SHA1 hashes: len = 897
0000: 02 00 00 4D 03 01 4D 04 B4 AE DE E4 AF 62 FA 48 ...M..M......b.H
0xxxxxx
0380: 00 .
main, WRITE: TLSv1 Handshake, length = 897
main, READ: TLSv1 Handshake, length = 141
*** Certificate chain
***
main, SEND TLSv1 ALERT: fatal, description = bad_certificate
main, WRITE: TLSv1 Alert, length = 2
main, called closeSocket()
main, handling exception: javax.net.ssl.SSLHandshakeException: null cert chain
main, IOException in getSession(): javax.net.ssl.SSLHandshakeException: null cert chain
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(Unknown Source)
at sslsocket.Server.getClientDistinguishedName(Server.java:86)
at sslsocket.Server.main(Server.java:37)回答 1
Stack Overflow用户
回答已采纳
发布于 2010-12-13 10:50:55
第一个SSL跟踪似乎是第二个跟踪的一部分，显示在服务器上。请确认。
第二个跟踪显示，服务器请求由“CN=xxxxxx Client，OU=communication，O=xxxxxx，L=Zuerich，ST=ZH，C=CH”签名的RSA或DSS证书，而客户端通过发送一个空证书链进行回复。这只能意味着客户端的密钥库中没有这样的证书，或者客户端没有使用正确的密钥库。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/4421536
复制相关文章
相似问题