From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: Florian.Weimer@RUS.Uni-Stuttgart.DE,
Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: Michael Bacarella <mbac@nyct.net>, linux-kernel@vger.kernel.org
Subject: Re: getpeereid() for Linux
Date: Wed, 5 Sep 2001 11:19:07 -0500 (CDT) [thread overview]
Message-ID: <200109051619.LAA58471@tomcat.admin.navo.hpc.mil> (raw)
Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>:
>
> Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil> writes:
>
> > It is not possible to get a creditential from TCP connections yet. That
> > requires an extension to IPSec to even be able to carry credentials. There
> > is no reliable communication path (even for identd) to be able to pass
> > credentials.
>
> I need the credentials only for local connections, though. This is
> technically possible. A userspace implementation partially cloning
> ident seems to be a possible approach.
It won't be reliable. Even the documentation for ident (at least the version
I looked at a while ago, might be different now, but I don't think so) says
that the data returned is not reliable. (even fuser doesn't always get this
right when trying to identify processes with open sockets).
Part of the problem is that TCP sockets don't carry the same information
that domain sockets have (could be partially wrong here, it just may not
be filled in since the source of the data can't supply it). The other
part is that it depends on what allocated the socket. Ownership is established
at socket allocation time, and the socket can be passed to a totally different
user. Identity of the user of the socket is therefore lost.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2001-09-05 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 16:19 Jesse Pollard [this message]
2001-09-05 16:36 ` 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
[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
2001-09-05 9:14 Florian Weimer
2001-09-05 13:38 ` Michael Bacarella
2001-09-05 14:35 ` 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=200109051619.LAA58471@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--cc=Florian.Weimer@RUS.Uni-Stuttgart.DE \
--cc=linux-kernel@vger.kernel.org \
--cc=mbac@nyct.net \
/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
all inboxes | Powered by JetHome®