Date: Wed, 27 May 2009 21:12:37 -0700 From: Zachary Loafman <zml@FreeBSD.org> To: Sujit K M <kmsujit@gmail.com> Cc: steven.danneman@isilon.com, freebsd-arch@freebsd.org Subject: Re: pthread_setugid_np Message-ID: <20090528041236.GA14687@isilon.com> In-Reply-To: <74fe56020905272039h6aed0724u38dbc25d0a1be6a7@mail.gmail.com> References: <20090528000147.GB3704@isilon.com> <74fe56020905271931l4c8d4677h3bbcce6d8c8a8605@mail.gmail.com> <20090528024640.GC9388@isilon.com> <74fe56020905272039h6aed0724u38dbc25d0a1be6a7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 28, 2009 at 09:09:28AM +0530, Sujit K M wrote: > These are posix unix standards that you are going to be implementing. > So if you are talking of only taking the interfaces, why is there any need > to have objections. pthread_setugid_np is a non-portable pthread extension for per-thread user/group impersonation on OS X. The _np on the function name is to indicate its lack of portability to other OSes - it is not part of any standard. There is no posix standard way to impersonate a user/group on a per-thread basis - and, in fact, the OS X pthread_setugid_np interface is the only one I know of in common use. I'm proposing introducing the same API and semantics to FreeBSD, thereby vaguely pushing it further towards a standard. I don't really claim it's the most elegant interface, though. -- Zach Loafman | Staff Engineer | Isilon Systems
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090528041236.GA14687>