Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uiucdcsb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcsb!grunwald
From: grunwald@uiucdcsb.UUCP
Newsgroups: net.unix
Subject: Re: New socket call suggestion
Message-ID: <19300026@uiucdcsb.UUCP>
Date: Wed, 19-Dec-84 19:18:00 EST
Article-I.D.: uiucdcsb.19300026
Posted: Wed Dec 19 19:18:00 1984
Date-Received: Fri, 21-Dec-84 02:02:19 EST
References: <732@sjuvax.UUCP>
Lines: 13
Nf-ID: #R:sjuvax:-73200:uiucdcsb:19300026:000:591
Nf-From: uiucdcsb!grunwald    Dec 19 18:18:00 1984

Re: putting the egid and euid in with the socket information

Other people have suggested this. Its needed for security reasons in a lot of
applications. However, I don't think you could do that and still use TCP/IP
since it's not in the definition. And a lot of people still want to use all
the wonderful features of TCP/IP.
	You can't do it in user space either -- needs to be in the kernel or
someone can intercept it. You'd have to define another protocol which
packages that information along with each socket. Perhaps a Secure-IP or
something along those lines.

Has anyone done this?