[Bug 594989] Re: Lucid Lynx authbind defaults too restrictive

2010-07-13 Thread Launchpad Bug Tracker
This bug was fixed in the package tomcat6 - 6.0.26-5 --- tomcat6 (6.0.26-5) unstable; urgency=medium * Convert patches to dep3 format. * Backport security fix from trunk to fix CVE-2010-1157. (Closes: #587447) * Set urgency to medium due to the security fix. tomcat6 (6.0.26-4)

[Bug 594989] Re: Lucid Lynx authbind defaults too restrictive

2010-06-24 Thread Thierry Carrez
** Changed in: tomcat6 (Ubuntu) Importance: Wishlist = Medium ** Changed in: tomcat6 (Ubuntu) Status: Confirmed = Triaged -- Lucid Lynx authbind defaults too restrictive https://bugs.launchpad.net/bugs/594989 You received this bug notification because you are a member of Ubuntu Server

[Bug 594989] Re: Lucid Lynx authbind defaults too restrictive

2010-06-24 Thread Thierry Carrez
Fix committed to debian java-svn ** Changed in: tomcat6 (Ubuntu) Status: Triaged = Fix Committed ** Changed in: tomcat6 (Ubuntu) Assignee: (unassigned) = Thierry Carrez (ttx) ** Changed in: tomcat6 (Ubuntu) Importance: Medium = Wishlist -- Lucid Lynx authbind defaults too

[Bug 594989] Re: Lucid Lynx authbind defaults too restrictive

2010-06-21 Thread Jason Brittain
Tom: That is in fact the behaviour I meant to configure authbind to allow -- I wanted to allow the Tomcat JVM to bind to privileged ports on any address on any NIC of the machine on which Tomcat runs. So, a network prefix of 0 is what it should use, instead of 32. Thanks for spotting that! --

[Bug 594989] Re: Lucid Lynx authbind defaults too restrictive

2010-06-16 Thread Thierry Carrez
** Changed in: tomcat6 (Ubuntu) Importance: Undecided = Wishlist ** Changed in: tomcat6 (Ubuntu) Status: New = Confirmed -- Lucid Lynx authbind defaults too restrictive https://bugs.launchpad.net/bugs/594989 You received this bug notification because you are a member of Ubuntu Server