2017-05-14 8 views
0

これは私にとって新しいドメインなので、利用可能な情報の解釈方法は完全にはわかりません。しかし、まだない私は私のJVMまたはJDK環境での設定を欠いていた場合、これはノイズであるかかどうかわからjarsigner -verify:警告メッセージ - BouncyCastle signed jar

Version 1.50 + WebStart: signature not verified

java SSL and cert keystore

研究は、以下の関連記事を生み出します。

これらのファイルは有効で安全に使用できますか?

警告メッセージを削除するには何が必要ですか?

私の質問は、私は、このコマンドによって生成され、次のメッセージの解釈はどうすればよいです:

jarsigner -verify -verbose -certs bcmail-jdk15on-157.jar 

は、次のような出力を生成します

s  11224 Thu May 11 17:31:18 EDT 2017 META-INF/MANIFEST.MF 
    X.509, CN=Legion of the Bouncy Castle Inc., OU=Java Software Code Signing, O=Sun Microsystems Inc 
    [certificate is valid from 3/10/17 8:15 PM to 4/25/20 3:00 AM] 
    X.509, CN=JCE Code Signing CA, OU=Java Software Code Signing, O=Sun Microsystems Inc, L=Palo Alto, ST=CA, C=US 
    [certificate is valid from 4/25/01 3:00 AM to 4/25/20 3:00 AM] 
    [CertPath not validated: Path does not chain with any of the trust anchors] 

    [entry was signed on 5/11/17 3:31 AM] 
    X.509, CN=Legion of the Bouncy Castle Inc., OU=Java Software Code Signing, O=Oracle Corporation 
    [certificate is valid from 3/10/17 8:07 PM to 3/10/22 8:07 PM] 
    X.509, CN=JCE Code Signing CA, OU=Java Software Code Signing, O=Oracle Corporation 
    [certificate is valid from 7/6/16 7:48 PM to 12/30/30 7:00 PM] 
    [CertPath not validated: Path does not chain with any of the trust anchors] 

    8546 Thu May 11 17:31:20 EDT 2017 META-INF/BC1024KE.SF 
    2221 Thu May 11 17:31:20 EDT 2017 META-INF/BC1024KE.DSA 
    8546 Thu May 11 17:31:18 EDT 2017 META-INF/BC2048KE.SF 
    6365 Thu May 11 17:31:18 EDT 2017 META-INF/BC2048KE.DSA 
     0 Thu May 11 17:30:54 EDT 2017 org/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/smime/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/smime/examples/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/smime/handlers/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/smime/util/ 
     0 Thu May 11 17:30:54 EDT 2017 org/bouncycastle/mail/smime/validator/ 
     sm  715 Thu May 11 17:27:56 EDT 2017 org/bouncycastle/mail/smime/CMSProcessableBodyPart.class 

    X.509, CN=Legion of the Bouncy Castle Inc., OU=Java Software Code Signing, O=Sun Microsystems Inc 
    [certificate is valid from 3/10/17 8:15 PM to 4/25/20 3:00 AM] 
    X.509, CN=JCE Code Signing CA, OU=Java Software Code Signing, O=Sun Microsystems Inc, L=Palo Alto, ST=CA, C=US 
    [certificate is valid from 4/25/01 3:00 AM to 4/25/20 3:00 AM] 
    [CertPath not validated: Path does not chain with any of the trust anchors] 

    [entry was signed on 5/11/17 3:31 AM] 
    X.509, CN=Legion of the Bouncy Castle Inc., OU=Java Software Code Signing, O=Oracle Corporation 
    [certificate is valid from 3/10/17 8:07 PM to 3/10/22 8:07 PM] 
    X.509, CN=JCE Code Signing CA, OU=Java Software Code Signing, O=Oracle Corporation 
    [certificate is valid from 7/6/16 7:48 PM to 12/30/30 7:00 PM] 
    [CertPath not validated: Path does not chain with any of the trust anchors] 
    . 
    . 
    . 
    s = signature was verified 
    m = entry is listed in manifest 
    k = at least one certificate was found in keystore 
    i = at least one certificate was found in identity scope 

    jar verified. 

    Warning: 
    This jar contains entries whose certificate chain is not validated. 
    This jar contains signatures that does not include a timestamp. Without a timestamp, users may not be able to validate this jar after the signer certificate's expiration date (2020-04-25) or after any future revocation date. 

答えて

0

はBouncyCastleが唯一の彼らの特別なコード署名でJARに署名セキュリティプロバイダの証明書。これはJavaのセキュリティプロバイダとしてJARを使用するために必要です。 BouncyCastleは、例えばJARに署名しません。アプレットまたはWebStartで実行します。あなたがそれを使用する必要がある場合などアプレットまたはWebStartで公開証明書を使用してのJAR に署名する必要があります。