Try redirecting port 80 to Tomcat's defaults:
http://jetty.mortbay.org/jetty/doc/User80.html
-Mensaje original-
De: Joe Tomcat [mailto:[EMAIL PROTECTED]]
Enviado el: viernes, 06 de septiembre de 2002 7:39
Para: Tomcat Users List
Asunto: Starting and stopping Tomcat as non-root
I am
Wow. Not to start a debate, but that's the silliest statement I've seen in
awhile.
If you don't like how it works, change it. You have the source.
John
-Original Message-
From: Joe Tomcat [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 06, 2002 1:39 AM
To: Tomcat Users List
Lately, I have been thinking of writing a JNI library to call setuid() and
setgid() to change the effective user ID and group ID of the process after
it starts.
I'm not sure how this would affect the various startup and shutdown scripts,
but it would be interesting from a security standpoint.
]
To: 'Tomcat Users List' [EMAIL PROTECTED]
Sent: Friday, September 06, 2002 8:50 AM
Subject: RE: Starting and stopping Tomcat as non-root
Wow. Not to start a debate, but that's the silliest statement I've seen
in
awhile.
If you don't like how it works, change it. You have the source.
John
]]
Sent: Friday, September 06, 2002 9:03 AM
To: Tomcat Users List
Subject: RE: Starting and stopping Tomcat as non-root
Lately, I have been thinking of writing a JNI library to call
setuid() and
setgid() to change the effective user ID and group ID of the
process after
it starts.
I'm
Alternatively, is there a way to make Linux so that it lets any user bind
to any port?
So you don't mind one of your machine's users (or a cracker who has
guessed a bad password) installing their own little fake webserver on port
80 that does {pick your poison}?
The practice of allowing only
