You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Daniel Walmsley <da...@firesyde.com> on 2008/01/21 07:34:42 UTC

Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

I blogged this, and Eelco wisely suggested I post it here. This is  
both a warning and plea for help - what's the best way to configure  
Tomcat on Debian for Wicket?

Was up until 3am last night banging my head against another  
frustrating go-nowhere issue deploying Wicket on Debian Etch’s default  
Tomcat5.5.

Apparently the latest version (5.5.20-2etch1) has additional security  
headaches features which prevent wicket from functioning properly out- 
of-the-box:

     * First of all, there’s still an (as-yet-unsolved) mystery around  
why I couldn’t get Wicket to start up as a filter. Just the mysterious  
“ERROR: filterStart” which makes me want to feed Tomcat to angry  
lions. Worked around it by using Wicket in Servlet mode instead.
     * Tomcat’s juli.jar can’t access WEB-INF/classes/ 
logging.properties. Fixed (in sledgehammer-like way) by adding  
“permission java.security.AllPermission;” to /etc/tomcat5.5/policy.d/ 
03catalina.policy, in the Juli section.
     * Tomcat security prevents webapps from accessing all sorts of  
features and methods by default, including wicket.properties, methods  
inside shipped jars, etc. Not being a Tomcat expert, and trusting the  
innate security of the server and millions of lines of third party  
code (i.e. I’m an idiot) I again just popped a  
java.security.AllPermission; in appropriate spots in /etc/tomcat5.5/ 
policy.d/04webapps.policy. Let the flames commence!

If Tomcat was a little more helpful in its error messages, this would  
never have been so painful. Jetty has always run my Wicket apps  
without complaint (though I’ve never tried the official Debian Jetty  
packages - maybe they’re crippleware secure too?).

The only reason I use Tomcat at all is the remote management and  
deployment features, which are well-supported by Cargo. Now that these  
issues are out of the way (mostly) I can take another few steps  
towards my dream of a seamless, fire-and-forget, auto-deploying, smoke- 
tested, pluggable and modular web app deployment system.

Any ideas on how to better configure Tomcat?

Any ideas on how to get more information about that ERROR: filterStart  
problem? I'd really like to do things the recommended way, instead of  
having to use WicketServlet.

Cheers,
Dan

Daniel Walmsley
Director, Firesyde
e: dan@firesyde.com
m: +61404864141




Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Martijn Dashorst <ma...@gmail.com>.
I think that most linux packagers don't work with Java projects and do
whatever they like. What Daniel is experiencing is an overzealous packager
that shuts down the most basic service tomcat needs to provide: run a web
application that does more than serve static pages. Packagers often make any
documentation that is available for a Java project worthless because they
move everything all over the disk.
This is akin to a mysql installation where you can't start a database and
run queries against.


Also, AFAIK 5.5.20 is about 1.5 years old. To me that is an indication that
packagers don't provide the most secure and workable solution, especially
when the latest 5.5.x (5.5.25) is already 6 months out.


Conservatism is a great thing for production servers, but running 1.5 years
behind the curve...?

Of course, the converse could be said for Java developers not getting linux
packaging, and in a sense we can learn a great deal from the tried and
tested unix package management. But even that is something that is still
evolving. For instance maven's repository infrastructure could (should?) be
pushed to a RPM/jpackage/apt service. The way I see it is that maven has
reinvented the wheel, and managed to make it a bit bumpier...

Martijn

On 1/21/08, C. Bergström < cbergstrom@netsyncro.com> wrote:
>
>
> On Mon, 2008-01-21 at 12:13 +0100, Martijn Dashorst wrote:
> > So your advise is to run a *very* outdated version because the packagers
>
> > haven't updated their software?
> > Sounds like a great way to open up your system to hackers.
>
> That's a very broad and sweeping statement.
>
>         1) I'm sure if there were known issues the distro package
> maintainer
> *should* issue an update with a fix
>         2) Looking at http://tomcat.apache.org/whichversion.html it
> appears 5.x
> is still supported
>
> I'll agree that a best practice to use latest stable, but not all
> organizations get it right living on the bleeding edge of custom
> packages and SVN Trunk or CVS HEAD if you prefer..
>
> I'm trying to give sensible advice that is generic enough to not lead
> someone astray or with other caveats which could result in bad pratices
> or more problems down the road.
>
> Now if I look at his original email and wonder why deb is still on
> 5.5.20-2etch1 when the apache site lists 5.5.25 as current I have no
> idea.
>
> ./C
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0

Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by "C. Bergström" <cb...@netsyncro.com>.
On Mon, 2008-01-21 at 12:13 +0100, Martijn Dashorst wrote:
> So your advise is to run a *very* outdated version because the packagers
> haven't updated their software?
> Sounds like a great way to open up your system to hackers.

That's a very broad and sweeping statement.

	1) I'm sure if there were known issues the distro package maintainer
*should* issue an update with a fix
	2) Looking at http://tomcat.apache.org/whichversion.html it appears 5.x
is still supported

I'll agree that a best practice to use latest stable, but not all
organizations get it right living on the bleeding edge of custom
packages and SVN Trunk or CVS HEAD if you prefer..

I'm trying to give sensible advice that is generic enough to not lead
someone astray or with other caveats which could result in bad pratices
or more problems down the road.

Now if I look at his original email and wonder why deb is still on
5.5.20-2etch1 when the apache site lists 5.5.25 as current I have no
idea.

./C


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Martijn Dashorst <ma...@gmail.com>.
So your advise is to run a *very* outdated version because the packagers
haven't updated their software?
Sounds like a great way to open up your system to hackers.

Martijn

On 1/21/08, C. Bergström <cb...@netsyncro.com> wrote:
>
>
> On Mon, 2008-01-21 at 11:31 +0100, Martijn Dashorst wrote:
> > You might want to skip the packaged version (IMO linux packagers don't
> > get the Java packaging), and just unzip a tarball
> > in /opt/tomcat/tomcat-5.5.20
> >
> >
> > Then you are in complete control over how the server runs.
> >
> -1
>
> Some distro packaging systems while admittedly are lacking in certain
> areas are there for a reason.
>
> 1) Tomcat is not perfect software and thus may have some security issue
> either in core or in the default context that's enabled by default and
> thus not everyone follows such alerts/advisories for a living. (Trusting
> that the distro will issue an update and the system is regularly
> maintained.)
> 2) I'm not sure this takes into account the install of tomcat native
> libs and also any distro related changes there
>
> etc etc...
> >
> > Martijn
> >
> <snip />
> >
> >
> >         Apparently the latest version ( 5.5.20-2etch1) has additional
> >         security headaches features which prevent wicket from
> >         functioning properly out-of-the-box:
>
> I consider this a positive thing as it means some forethought has
> actually gone into this package.
>
> <snip />
>
> >
> >         Any ideas on how to better configure Tomcat?
>
> Not at the moment.  The best I can offer is give me about a week and
> I'll see if I can get deb etch installed in vmware and have a look.
>
>
> Good luck,
>
> ./C
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0

Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Eelco Hillenius <ee...@gmail.com>.
OT...

>         1) I don't use debian (and was trying to be helpful)

Always welcome.

>         2) My distro of choice *does* have tc 6 (which I'm not sure matters in
> this case)

Just curious, what is your distro of choice?

>         3) I don't use tc for production

Again just curious, what is your app server of choice (and why)?

Cheers,

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by "C. Bergström" <cb...@netsyncro.com>.
On Mon, 2008-01-21 at 12:28 +0100, Johan Compagner wrote:
> Completely not working is a great security fix yes...
> If that distro is still in 5.5 mode then i question there updates

Here's the wishlist item for why there isn't currently 6.x in deb etch

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413906

>>From what I can tell this package is pretty diligently updated for
security issues and saying anything about 5.5.x being a hackers risk is
fud unless it can be backed up with evidence.
http://packages.debian.org/stable/allpackages?format=txt.gz


Since others know best I'm going to step aside on this.  I assume this
is a user configuration issue, but

	1) I don't use debian (and was trying to be helpful)
	2) My distro of choice *does* have tc 6 (which I'm not sure matters in
this case)
	3) I don't use tc for production


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Johan Compagner <jc...@gmail.com>.
Completely not working is a great security fix yes...
If that distro is still in 5.5 mode then i question there updates

On 1/21/08, C. Bergström <cb...@netsyncro.com> wrote:
>
> On Mon, 2008-01-21 at 11:31 +0100, Martijn Dashorst wrote:
> > You might want to skip the packaged version (IMO linux packagers don't
> > get the Java packaging), and just unzip a tarball
> > in /opt/tomcat/tomcat-5.5.20
> >
> >
> > Then you are in complete control over how the server runs.
> >
> -1
>
> Some distro packaging systems while admittedly are lacking in certain
> areas are there for a reason.
>
> 1) Tomcat is not perfect software and thus may have some security issue
> either in core or in the default context that's enabled by default and
> thus not everyone follows such alerts/advisories for a living. (Trusting
> that the distro will issue an update and the system is regularly
> maintained.)
> 2) I'm not sure this takes into account the install of tomcat native
> libs and also any distro related changes there
>
> etc etc...
> >
> > Martijn
> >
> <snip />
> >
> >
> >         Apparently the latest version ( 5.5.20-2etch1) has additional
> >         security headaches features which prevent wicket from
> >         functioning properly out-of-the-box:
>
> I consider this a positive thing as it means some forethought has
> actually gone into this package.
>
> <snip />
>
> >
> >         Any ideas on how to better configure Tomcat?
>
> Not at the moment.  The best I can offer is give me about a week and
> I'll see if I can get deb etch installed in vmware and have a look.
>
>
> Good luck,
>
> ./C
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

-- 
Sent from Gmail for mobile | mobile.google.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by "C. Bergström" <cb...@netsyncro.com>.
On Mon, 2008-01-21 at 11:31 +0100, Martijn Dashorst wrote:
> You might want to skip the packaged version (IMO linux packagers don't
> get the Java packaging), and just unzip a tarball
> in /opt/tomcat/tomcat-5.5.20
> 
> 
> Then you are in complete control over how the server runs.
> 
-1

Some distro packaging systems while admittedly are lacking in certain
areas are there for a reason.

1) Tomcat is not perfect software and thus may have some security issue
either in core or in the default context that's enabled by default and
thus not everyone follows such alerts/advisories for a living. (Trusting
that the distro will issue an update and the system is regularly
maintained.)
2) I'm not sure this takes into account the install of tomcat native
libs and also any distro related changes there

etc etc...
> 
> Martijn
> 
<snip />
>         
>          
>         Apparently the latest version ( 5.5.20-2etch1) has additional
>         security headaches features which prevent wicket from
>         functioning properly out-of-the-box:

I consider this a positive thing as it means some forethought has
actually gone into this package.

<snip />

>          
>         Any ideas on how to better configure Tomcat?

Not at the moment.  The best I can offer is give me about a week and
I'll see if I can get deb etch installed in vmware and have a look.


Good luck,

./C


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by "C. Bergström" <cb...@netsyncro.com>.
On Mon, 2008-01-21 at 11:52 +0100, Johan Compagner wrote:
> Take then the latest 6
> 5 is getting pretty old

I know from first hand experience with a couple Linux distros are still
on 5 as it's 'stable'.  More to the point is that they probably can't
support slotted upgrades where half of the community wants 5.x and the
other half wants 6.x so they are erring on the conservative side.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Johan Compagner <jc...@gmail.com>.
Take then the latest 6
5 is getting pretty old

On 1/21/08, Martijn Dashorst <ma...@gmail.com> wrote:
> You might want to skip the packaged version (IMO linux packagers don't get
> the Java packaging), and just unzip a tarball in /opt/tomcat/tomcat-5.5.20
> Then you are in complete control over how the server runs.
>
> Martijn
>
> On 1/21/08, Daniel Walmsley <da...@firesyde.com> wrote:
> >
> > I blogged this, and Eelco wisely suggested I post it here. This is both a
> > warning and plea for help - what's the best way to configure Tomcat on
> > Debian for Wicket?
> >
> >
> > Was up until 3am last night banging my head against another frustrating
> > go-nowhere issue deploying Wicket on Debian Etch's default Tomcat5.5.
> >
> >
> > Apparently the latest version (5.5.20-2etch1) has additional security
> > headaches features which prevent wicket from functioning properly
> > out-of-the-box:
> >
> >
> >     * First of all, there's still an (as-yet-unsolved) mystery around why
> > I couldn't get Wicket to start up as a filter. Just the mysterious "ERROR:
> > filterStart" which makes me want to feed Tomcat to angry lions. Worked
> > around it by using Wicket in Servlet mode instead.
> >     * Tomcat's juli.jar can't access WEB-INF/classes/logging.properties.
> > Fixed (in sledgehammer-like way) by adding "permission
> > java.security.AllPermission;" to
> > /etc/tomcat5.5/policy.d/03catalina.policy, in the Juli section.
> >     * Tomcat security prevents webapps from accessing all sorts of
> > features and methods by default, including wicket.properties, methods
> > inside shipped jars, etc. Not being a Tomcat expert, and trusting the
> innate
> > security of the server and millions of lines of third party code (i.e. I'm
> > an idiot) I again just popped a java.security.AllPermission; in
> > appropriate spots in /etc/tomcat5.5/policy.d/04webapps.policy. Let the
> > flames commence!
> >
> >
> > If Tomcat was a little more helpful in its error messages, this would
> > never have been so painful. Jetty has always run my Wicket apps without
> > complaint (though I've never tried the official Debian Jetty packages -
> > maybe they're crippleware secure too?).
> >
> >
> > The only reason I use Tomcat at all is the remote management and
> > deployment features, which are well-supported by Cargo. Now that these
> > issues are out of the way (mostly) I can take another few steps towards my
> > dream of a seamless, fire-and-forget, auto-deploying, smoke-tested,
> > pluggable and modular web app deployment system.
> >
> >
> > Any ideas on how to better configure Tomcat?
> >
> >
> > Any ideas on how to get more information about that ERROR: filterStart
> > problem? I'd really like to do things the recommended way, instead of
> having
> > to use WicketServlet.
> >
> >
> > Cheers,
> > Dan
> >
> > *Daniel Walmsley
> > Director, Firesyde <http://firesyde.com/>
> > e: dan@firesyde.com
> > m: +61404864141
> > *
> >
> >
> >
> >
>
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0
>

-- 
Sent from Gmail for mobile | mobile.google.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Security violations and "ERROR: filterStart" with Tomcat deployment on Debian Etch

Posted by Martijn Dashorst <ma...@gmail.com>.
You might want to skip the packaged version (IMO linux packagers don't get
the Java packaging), and just unzip a tarball in /opt/tomcat/tomcat-5.5.20
Then you are in complete control over how the server runs.

Martijn

On 1/21/08, Daniel Walmsley <da...@firesyde.com> wrote:
>
> I blogged this, and Eelco wisely suggested I post it here. This is both a
> warning and plea for help - what's the best way to configure Tomcat on
> Debian for Wicket?
>
>
> Was up until 3am last night banging my head against another frustrating
> go-nowhere issue deploying Wicket on Debian Etch's default Tomcat5.5.
>
>
> Apparently the latest version (5.5.20-2etch1) has additional security
> headaches features which prevent wicket from functioning properly
> out-of-the-box:
>
>
>     * First of all, there's still an (as-yet-unsolved) mystery around why
> I couldn't get Wicket to start up as a filter. Just the mysterious "ERROR:
> filterStart" which makes me want to feed Tomcat to angry lions. Worked
> around it by using Wicket in Servlet mode instead.
>     * Tomcat's juli.jar can't access WEB-INF/classes/logging.properties.
> Fixed (in sledgehammer-like way) by adding "permission
> java.security.AllPermission;" to
> /etc/tomcat5.5/policy.d/03catalina.policy, in the Juli section.
>     * Tomcat security prevents webapps from accessing all sorts of
> features and methods by default, including wicket.properties, methods
> inside shipped jars, etc. Not being a Tomcat expert, and trusting the innate
> security of the server and millions of lines of third party code (i.e. I'm
> an idiot) I again just popped a java.security.AllPermission; in
> appropriate spots in /etc/tomcat5.5/policy.d/04webapps.policy. Let the
> flames commence!
>
>
> If Tomcat was a little more helpful in its error messages, this would
> never have been so painful. Jetty has always run my Wicket apps without
> complaint (though I've never tried the official Debian Jetty packages -
> maybe they're crippleware secure too?).
>
>
> The only reason I use Tomcat at all is the remote management and
> deployment features, which are well-supported by Cargo. Now that these
> issues are out of the way (mostly) I can take another few steps towards my
> dream of a seamless, fire-and-forget, auto-deploying, smoke-tested,
> pluggable and modular web app deployment system.
>
>
> Any ideas on how to better configure Tomcat?
>
>
> Any ideas on how to get more information about that ERROR: filterStart
> problem? I'd really like to do things the recommended way, instead of having
> to use WicketServlet.
>
>
> Cheers,
> Dan
>
> *Daniel Walmsley
> Director, Firesyde <http://firesyde.com/>
> e: dan@firesyde.com
> m: +61404864141
> *
>
>
>
>



-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0