Slackware Linux
Well, no way is a bit strong a statement. For
example Linux' netfilter
provides an owner match for locally generated packets. This
should be
usable to indeed create a per-user restriction of access to
the shutdown
port.
But since the OP didn't bother to tell us which OS
for the response,
Fu-Tung
--- On Thu, 8/21/08, Mark Thomas [EMAIL PROTECTED] wrote:
From: Mark Thomas [EMAIL PROTECTED]
Subject: Re: tomcat instances on different ports running as different users
can anyone shutdown?
To: Tomcat Users List users@tomcat.apache.org
Date: Thursday, August 21, 2008
Hi,
I have different instances of tomcat running on different ports of the same
machine. The processes are running as different users. In this case could a
user different than the one who launched the process connect to the tomcat
shutdown port and cause the other instance to shutdown?
It
Fu-Tung Cheng wrote:
Hi,
I have different instances of tomcat running on different ports of the same
machine. The processes are running as different users. In this case could a
user different than the one who launched the process connect to the tomcat
shutdown port and cause the other
any changes to the code in order
to set this up how I want it to work.
Fu-Tung
--- On Thu, 8/21/08, André Warnier [EMAIL PROTECTED] wrote:
From: André Warnier [EMAIL PROTECTED]
Subject: Re: tomcat instances on different ports running as different users
can anyone shutdown?
To: Tomcat Users
On Thu, Aug 21, 2008 at 1:07 PM, Fu-Tung Cheng [EMAIL PROTECTED] wrote:
I am sure there must be an option in the stop script to require a
username/password.
And I'm sure that wouldn't matter -- it's simply a matter of telneting to
that port and issuing the shutdown command, no script required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fu-Tung,
Fu-Tung Cheng wrote:
I have different instances of tomcat running on different ports of
the same machine. The processes are running as different users. In
this case could a user different than the one who launched the
process connect
Christopher Schultz schrieb:
As Andre points out, there is no way to restrict TCP/IP ports to certain
users.
Well, no way is a bit strong a statement. For example Linux' netfilter
provides an owner match for locally generated packets. This should be
usable to indeed create a per-user
The simple solution (from Filip):
Set the shutdown port to -1.
Use kill to stop Tomcat.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
