Correction for first mail of this morning :
Resolution :
sudo chown tomcat7 /var/lib/tomcat7/conf/jmxremote.password
sudo chmod 600 /var/lib/tomcat7/conf/jmxremote.password
sudo service tomcat7 restart
(sorry bad copy/paste)
2016-06-27 11:34 GMT+02:00 David_dev Dev <dcpc@gmail.
Hi,
I'd prefer not change default config and current install (will need to
change template, deploy scripts and internal docs to :-( ), and in
precedent answers someone onawer that's this chown is not recommanded and
should have been change :
"So in my opinion we should stop chowning
Hi,
This morning we apply the security patch on our debian 7 servers, and ALL
our tomcat7 crash !
Exactly the same problem, the patch overwrite the owner of ALL /etc/tomcat7
file, includind jmxremote.password to root:tomcat7.
I see in the bug that you should have change this configuration.
Hi,
Thx for the answer.
the jmxremote.password 600 mode is a mandatory from Tomcat configuration.
Is set to another mode tomcat will not start.
It's the same as the ~/.ssh/id_rsa configuration.
Some corrections on the following answer :
- the script chown root:tomcat7 (and not root:root).
I
I found the chown in the /var/lib/dpkg/info/tomcat7.postinst. not really
sure if it's in the tomcat7-admin package
# configuration files should not be modifiable by tomcat7 user, as
this can be a security issue
# (an attacker may insert code in a webapp and have access to
5 matches
Mail list logo
