Date: Thu, 13 Dec 2001 22:17:50 -0500 (EST) From: Robert Watson <rwatson@freebsd.org> To: Dima Dorfman <dima@trit.org> Cc: "Brian F. Feldman" <green@freebsd.org>, arch@freebsd.org Subject: Re: MFC'ing xucred definition Message-ID: <Pine.NEB.3.96L.1011213221643.74588G-100000@fledge.watson.org> In-Reply-To: <20011214031351.6D1203E2F@bazooka.trit.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Dec 2001, Dima Dorfman wrote:
> > Actually, the one thing I'd like to see before we move forward is a
> > standard routine that accepts a ucred, and a *xucred, and fills out the
> > xucred using the ucred (preferably, in kern_prot.c). Right now, xucred is
> > filled out in various places manually (netinet, socket code, et al). As
> > we begin to broaden the scope of xucred (for example, I'd like to push in
> > the ruid and rgid), it will make things a lot easier, and also prevent
> > more code from knowing much about the innards of ucred. That way, also,
> > the version number can be kept in one place.
>
> I had patches to add this routine (and vice versa, xucred->ucred)
> before you added the extra fields to ucred, at which point I dropped it
> since it didn't make much sense: Which fields do you copy? Effective,
> real, or saved {u,g}ids? It would again make sense if xucred had the
> same set of fields as ucred, however.
It's always been euid in ucred previously, so I assumed that for version 0
of xucred, only euid and egid (plus additional groups) would be exported.
Future versions of xucred (probably version 1, only in -CURRENT) would
also be able to export ruid, svuid, rgid, and svgid.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
robert@fledge.watson.org NAI Labs, Safeport Network Services
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1011213221643.74588G-100000>