On Fri, May 04, 2001 at 08:34:57PM -0700, Alfred Perlstein wrote:
> The silly part of it is that the socket's initial credentials
> might be different than the holder's credentials.
A user calls connect() with one set of credentials, subsequently changes
credentials, and writes to the socket.
On Fri, May 04, 2001 at 05:07:38PM -0700, Alfred Perlstein wrote:
> * Dima Dorfman <[EMAIL PROTECTED]> [010504 16:06] wrote:
> > Is there a reliable method of obtaining the credentials (uid/gid) of a
> > peer (SOCK_STREAM sockets only, obviously) on a unix domain socket?
> > All the Stevens books
On Tue, Aug 08, 2000 at 11:28:16AM -0700, Peter Wemm wrote:
>
> Passing only one gid is nearly useless. You should copy them all or not
> at all. I would like to see real and effective uid's as well.
Completeness certainly has its appeal, but is it necessary? What can
you not accomplish witho
With getpeereid() the credentials are passed at connect() and do not
require the client to send data. Therefore clients cannot consume
connections anonymously.
W.
On Tue, Aug 08, 2000 at 09:35:28AM -0700, Alfred Perlstein wrote:
>
> I haven't used the credential passing feature of sendmsg(), b
A patch implementing a getpeereid() syscall in FreeBSD 4.0 is
available at
http://www.superscript.com/patches/freebsd_4_0.getpeereid
A local-domain server uses getpeereid() to obtain client credentials.
Based on getpeereid() I created ucspi-ipc, a local-domain analogue to
Dan Bernstein's ucspi-t
5 matches
Mail list logo
