> The exploit managed to start inetd, camped on the specified port I guess, if it doesn't exist already, that it wouldn't be so hard to create a small patch to the kernel, so that only processes owned by root, or a certain group of users (let's say "daemon"), were allowed to set up listeners... walter -- Walter W. Hop <[EMAIL PROTECTED]> | +31 6 24290808 | NEW KEY: 0x84813998 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Protections on inetd (and /sbin/* /usr/sbin/* in gene... Michael R. Wayne
- Re: Protections on inetd (and /sbin/* /usr/sbin/... Dima Dorfman
- Re: Protections on inetd (and /sbin/* /usr/sbin/... Walter W. Hop
- Re: Protections on inetd (and /sbin/* /usr/s... Peter Pentchev
- Re: Protections on inetd (and /sbin/* /u... David Malone
- Re: Protections on inetd (and /sbin/... Peter Pentchev
- Re: Protections on inetd (and /sbin/* /u... Aleksandr A.Babaylov
- Re: Protections on inetd (and /sbin/... mouss
- Re: Protections on inetd (and /... Matt Dillon
- Re: Protections on inetd (a... Dag-Erling Smorgrav
- Re: Protections on inetd (and /sbin/* /usr/s... mouss
- Re: Protections on inetd (and /sbin/* /usr/sbin/... Daniel C. Sobral
- Re: Protections on inetd (and /sbin/* /usr/sbin/... Gordon Tetlow