Just for future reference to others, the problem was this line in
Funambol data synchronization server's start.sh script:
JAVA_OPTS=$JAVA_OPTS
-Djavax.net.ssl.trustStore=$FUNAMBOL_HOME/lib/security/cacerts
Commenting this out fixed the problem. I still fail to see how this
should affect the
From: Samuli Seppänen [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat 5.5 and SSL connector: keystore was
tampered with [SOLVED]
Tomcat SSL Connector entries accept the following parameters:
- keystorePass (password for the JKS (Java keystore)
- keypass (password for the key inside the JKS
-
I had no problems running with a password other than changeit on any of
5.5.23, 5.5.25, and various 6.0.x levels. As long as the keystore is built with both
passwords the same, everything functions as documented.
Take a look at Troubleshooting section in
http://tomcat.apache.org/tomcat-5.5-du
From: Samuli Seppänen [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat 5.5 and SSL connector: keystore was
tampered with [SOLVED]
I suppose this Tomcat home does not apply if I use absolute
pathnames, like /root/newkeystore?
There's always a home directory for the process, usually based on
From: Samuli Seppänen [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat 5.5 and SSL connector: keystore was
tampered with [SOLVED]
My only problem has been the requirement to use the
default password changeit.
I had no problems running with a password other than changeit on any of
5.5.23,
Update on this thing Tomcat+SSL+keystore thing:
I dug into the Tomcat 5.5.25 source code to see what's really going on.
Here's what I found - hopefully it's useful to someone.
Tomcat SSL Connector entries accept the following parameters:
- keystorePass (password for the JKS (Java keystore)
-
From: Samuli Seppänen [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat 5.5 and SSL connector: keystore was
tampered with [SOLVED]
Tomcat SSL Connector entries accept the following parameters:
- keystorePass (password for the JKS (Java keystore)
- keypass (password for the key inside the JKS
