Thanks Eduardo.
Updated all our systems and it worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170
Title:
tomcat7 doesn't start after upgrade to 7.0.68-1ubuntu0.3
To manage notificat
This bug was fixed in the package tomcat7 - 7.0.68-1ubuntu0.4
---
tomcat7 (7.0.68-1ubuntu0.4) xenial-security; urgency=medium
* SECURITY REGRESSION: security manager startup issue (LP: #170)
- debian/patches/0009-Use-java.security.policy-file-in-catalina.sh.patch:
upda
Thanks SWick!
Tomcat7 with the fix published, should reach in the repositories in a
few minutes.
Thanks for all the feedback and in case of problems just let us know!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Looks good
- Installed a fresh Xenial VM
- Installed tomcat7
- Enabled security manager
- Restarted tomcat7 -> won't start
- Installed the .deb's from the PPA manually
- tomcat7 starts again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Can anyone test the tomcat7 built here:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages
My tests were successful but I would appreciate more feedback about it.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thank you all for reporting the issue and sorry that it affected you.
I'm already working on the fix and will let you know here if you can also test
it before we publish it in the repository.
>From what I've looked this is a Xenial issue only, so I am marking Trusty as
>Invalid.
** Changed in:
Yes it was a "normal" security update via "apt-get upgrade" from tomcat7
(7.0.68-1ubuntu0.1) to tomcat7 (7.0.68-1ubuntu0.3) on a Xenial system...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170
Yeah ok, I see how "apt update && apt upgrade" will strip your workaround from
the system.
Thanks for clarifying.
My analysis agrees to everything else.
Thanks for additionally pointing out the sourcing of /etc/default/tomcat7 and
most importantly the $POLICY_CACHE at
POLICY_CACHE="$CATALINA_BA
upgrade in this context means: "apt update && apt upgrade", so just a
regular security update, not from any older distribution
/etc/init.d/tomcat7 sources /etc/default/tomcat7 (line 111-114) so
TOMCAT7_SECURITY is read from their.
The conffile will be created from postinst in tomcat7_7.0.68-1ubun
The script would usually call tomcat with:
-Djava.security.policy=="$CATALINA_BASE"/work/catalina.policy
The dir here by the suggested sed is replaced by
work -> policy
Many other things are referenced based on "$CATALINA_BASE/..." and they
are all in "/var/lib/tomcat7/...".
So is the genera
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tomcat7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/170
Title:
to
11 matches
Mail list logo
