2 .\" Copyright (c) 2001 Dima Dorfman.
 
   3 .\" All rights reserved.
 
   5 .\" Redistribution and use in source and binary forms, with or without
 
   6 .\" modification, are permitted provided that the following conditions
 
   8 .\" 1. Redistributions of source code must retain the above copyright
 
   9 .\"    notice, this list of conditions and the following disclaimer.
 
  10 .\" 2. Redistributions in binary form must reproduce the above copyright
 
  11 .\"    notice, this list of conditions and the following disclaimer in the
 
  12 .\"    documentation and/or other materials provided with the distribution.
 
  14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 
  15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 
  16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 
  17 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 
  18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 
  19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 
  20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 
  21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 
  22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 
  23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 
  26 .\" $FreeBSD: src/lib/libc/gen/getpeereid.3,v 1.6 2002/12/18 10:13:54 ru Exp $
 
  33 .Nd get the effective credentials of a UNIX-domain peer
 
  40 .Fn getpeereid "int s" "uid_t *euid" "gid_t *egid"
 
  44 function returns the effective user and group IDs of the
 
  61 The effective used ID is placed in
 
  63 and the effective group ID in
 
  66 The credentials returned to the
 
  68 caller are those of its peer at the time it called
 
  70 the credentials returned to the
 
  72 caller are those of its peer at the time it called
 
  74 This mechanism is reliable; there is no way for either side to influence
 
  75 the credentials returned to its peer except by calling the appropriate
 
  76 system call (i.e., either
 
  80 under different effective credentials.
 
  82 One common use of this routine is for a
 
  85 to verify the credentials of its client.
 
  86 Likewise, the client can verify the credentials of the server.
 
  87 .Sh IMPLEMENTATION NOTES
 
  91 is implemented in terms of the
 
 106 is not a valid descriptor.
 
 110 is a file, not a socket.
 
 114 does not refer to a socket on which
 
 122 does not refer to a socket of type
 
 124 or the kernel returned invalid data.