the easy way could be (probably) force the ftp daemon run as some
other user, or assign a second IP to the server and make sure that
the ftpd binds to the second address.
But in the end, one probably might also like to have a separate
namespace where processes can [be forced to] register and who
On Tue, Jan 02, 2001 at 01:14:18AM +0100, Anders Nordby wrote:
> FYI I am running 4.1.1-STABLE as of Tue Oct 24 01:25:55 CEST 2000, and top(1)
> shows all proftpd processes as being owned by root.
If I filter on uid root, the rules will match the packets (I tried with
specific IPs + uid root):
0
On Mon, Jan 01, 2001 at 05:24:09PM -0600, Bill Fumerola wrote:
>> Are people actually using uid type rules heavily? I'm having trouble matching
>> the packets generated by programs like Apache and ProFTPD. I believe that may
>> be because of root binding the ports these programs use before they se
On Mon, Jan 01, 2001 at 09:08:26PM +0100, Anders Nordby wrote:
> Are people actually using uid type rules heavily? I'm having trouble matching
> the packets generated by programs like Apache and ProFTPD. I believe that may
> be because of root binding the ports these programs use before they setu
Hello,
Are people actually using uid type rules heavily? I'm having trouble matching
the packets generated by programs like Apache and ProFTPD. I believe that may
be because of root binding the ports these programs use before they setuid() or
something, I'm not sure. Particularly I have trouble m
