On Wed, 18 Aug 1999, Tomi Manninen OH2BNS wrote: > I don't see the need for such an elaborate arrangement, at least if the > only reason was to replace the current "listen". Listen has no user > interaction and it should be pretty easy to make sure it has no buffer > overflows or other security risks. As a small security measure which might save us from a part of the risk of buffer overflows, listen could 1) open the raw socket, 2) check if real uid != 0 and effective uid == 0 then set euid = real uid; since being root is only required in listen for opening the socket, right? - Hessu
- listen utility and permissions Gerard Parat
- Re: listen utility and permissions Richard Adams
- Re: listen utility and permissions Bob Meyer
- Re: listen utility and permissions Tomi Manninen
- Re: listen utility and permissions Hamish Moffatt
- Re: listen utility and permissi... Craig Small
- Re: listen utility and perm... Gerd
- Re: listen utility and ... Tomi Manninen OH2BNS
- Re: listen utility and ... Michele A Debandi
- Re: listen utility and ... Heikki Hannikainen
- Re: listen utility and ... Gerd
- Re: listen utility and ... Heikki Hannikainen
- Re: listen utility and ... Gerd
- Re: listen utility and ... Tomi Manninen OH2BNS
- Re: listen utility and ... Gerd
- Re: listen utility and ... Ronnie Hale
- Re: listen utility and ... Bob Meyer
- Re: listen utility and ... Ronnie Hale
- Re: listen utility and ... Gerd
- Re: listen utility and ... Tomi Manninen OH2BNS
