I haven't seen anything in the log related to signature verification even i
wrote the wrong certificate alias in the catalina.policy file. the
resultant log will be the same
INFO - Loaded APR based Apache Tomcat Native library 1.1.32 using APR
version 1.5.1.
INFO - APR capabilities: IPv6 [true]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sanaullah,
On 2/19/15 12:26 PM, Sanaullah wrote:
>> Can you verify that the certificate is in there by doing
>> "keytool - -list .../cacerts"?
>
> keytool -v --list -keystore
> /usr/lib/jvm/jdk1.8.0_25/jre/lib/security/cacerts |grep
> "codesigntes
>Can you verify that the certificate is in there by doing "keytool
>- -list .../cacerts"?
keytool -v --list -keystore
/usr/lib/jvm/jdk1.8.0_25/jre/lib/security/cacerts |grep "codesigntest"
Enter keystore password:
Alias name: codesigntest
Owner: CN=codesigntest
>> I mentioned the same alias in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sanaullah,
On 2/19/15 10:28 AM, Sanaullah wrote:
> I have imported the public key (singed certificate) of the code
> signing certificate using keytool to JVM cacerts
> "/usr/lib/jvm/jdk1.8.0_25/jre/lib/security/cacerts" and certificate
> alias nam
Hey Chris,
I have imported the public key (singed certificate) of the code signing
certificate using keytool to JVM cacerts
"/usr/lib/jvm/jdk1.8.0_25/jre/lib/security/cacerts" and certificate alias
name is "codesigntest"
I mentioned the same alias in in catalina.policy
grant signedBy "codesignt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sanaullah,
On 2/13/15 12:48 PM, Sanaullah wrote:
> I have signed the ear package using jar signer and start the tomee
> using ./startup.sh -security and also edit the catalina.policy
> file looks like below.
>
> I am confused here, how code sign v
