From: Michael Bacarella <mbac@nyct.net>
To: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: getpeereid() for Linux
Date: Wed, 5 Sep 2001 09:38:51 -0400 [thread overview]
Message-ID: <20010905093851.A24280@sync.nyct.net> (raw)
In-Reply-To: <tgsne23sou.fsf@mercury.rus.uni-stuttgart.de>
In-Reply-To: <tgsne23sou.fsf@mercury.rus.uni-stuttgart.de>
> Would anyone like to give me a helping hand in implementing the
> getpeereid() syscall for Linux? See the following page for the
> documentation of the OpenBSD implementation:
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=getpeereid&sektion=2&apropos=0&manpath=OpenBSD+Current
>
> I think I could work out the kernel data structures to gather the
> relevant data from, however, I won't get all the locking stuff right.
>
> OTOH, is there any chance that the addition of such a syscall would be
> accepted?
There's no need. The equivalent functionality can already be
implemented in userspace.
------
#include <sys/socket.h>
uid_t getpeereuid(int sd)
{
struct ucred cred;
int len = sizeof (cred);
if (getsockopt(sd,SOL_SOCKET,SO_PEERCRED,&cred,&len))
return -1;
return cred.uid;
}
------
The same can be done for gid, and even pid.
Yes, Linux rules.
--
Michael Bacarella <mbac@nyct.net>
Technical Staff / System Development,
New York Connect.Net, Ltd.
next prev parent reply other threads:[~2001-09-05 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 9:14 getpeereid() for Linux Florian Weimer
2001-09-05 13:38 ` Michael Bacarella [this message]
2001-09-05 14:35 ` Florian Weimer
[not found] <tgsne23sou.fsf@mercury.rus.uni-stuttgart.de.suse.lists.linux.kernel>
2001-09-05 9:52 ` Andi Kleen
2001-09-05 10:05 ` Florian Weimer
2001-09-05 10:48 ` Andi Kleen
2001-09-05 10:56 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 15:51 Jesse Pollard
2001-09-05 15:53 ` Florian Weimer
2001-09-05 20:26 ` H. Peter Anvin
2001-09-05 16:19 Jesse Pollard
2001-09-05 16:36 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010905093851.A24280@sync.nyct.net \
--to=mbac@nyct.net \
--cc=Florian.Weimer@RUS.Uni-Stuttgart.DE \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox