Re: [PATCH] Ownership of sockets 2.4.0-test2

From: Christoffer Hall-Frederiksen (hall@diku.dk)
Date: Thu Jul 06 2000 - 18:30:32 EST


On Thu, Jul 06, 2000 at 09:16:38PM +0100, Alan Cox wrote:
> So its a problem to sort out with ident

OK.

> Another point is that an rlogin/rsh type tool should be dropping setuidness
> and keeping just the capability for low ports on a current kernel..

Yes, but not in thes case ;)
You have to drop privileges after calling bind, then the owner of
the socket is set.

The only thing an application can do right now is do a setfsuid, right?

That solves the 'problem' right now. It could call setfsuid before
socket and bind. inet_bind goes for the euid in capaple, not the fsuid.

It's not pretty, but what the heck.

Thank you for the patient answers.

-- 
	Christoffer

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:19 EST