From: Kodungallur Varma <ramgwu@gmail.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: attributes on the other end of a network connection
Date: Wed, 4 May 2005 11:30:54 -0400 [thread overview]
Message-ID: <fa8ec5d805050408307808096b@mail.gmail.com> (raw)
In-Reply-To: <1113999576.1028.41.camel@moss-spartans.epoch.ncsc.mil>
Hi Stephen and all,
is there any way to determine if a particular operation is
permitted given a security identifier (security_context_t)? basically
I want a function or a way to determine if any process/user in the
domain returned by the getpeercon() is allowed to do an operation, say
socket connect for example.
thanx..
Ram
On 4/20/05, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On Tue, 2005-04-19 at 22:09 -0400, Kodungallur Varma wrote:
> > Hi all,
> >
> > I have a basic client and a server program. my server has the
> > capability to setcon() to a new domain, the client domain precisely.
> > my server needs to find the domain and user name of the client user(my
> > client tries to get a tcp connection first). I heard there is a
> > function which gives the context and attributes of the other end,
> > given the attributes got at the servers end and vice-versa. I dont
> > know where exactly to look for that function capability, but I am
> > starting in the libselinux library. for security reasons, my client
> > also needs to be able to execute this function to get the attributes
> > of the server, just to know that it is connecting to the right server.
> > if anyone knows about any such function, please pass on to me. thanx a lot..
>
> That requires some form of labeled networking support, which doesn't
> exist in the mainline SELinux presently. Older SELinux had an
> experimental labeled networking implementation (Selopt) by James Morris
> based on CIPSO/FIPS188 options, but the necessary security hooks and
> fields weren't accepted into mainline Linux. Trent Jaeger of IBM has
> implemented implicit packet labeling based on IPSEC SA, and I believe
> that there is work ongoing to provide such an interface using that
> support, but that hasn't been merged yet. getpeercon(3) is the existing
> interface, but only works for Unix domain stream sockets presently, as
> James noted.
>
> --
> Stephen Smalley <sds@tycho.nsa.gov>
> National Security Agency
>
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2005-05-04 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 4:08 problems using setcon() Kodungallur Varma
2005-03-09 8:46 ` Thomas Bleher
2005-03-12 2:35 ` Kodungallur Varma
2005-03-14 15:06 ` Stephen Smalley
2005-03-29 3:55 ` Kodungallur Varma
2005-03-29 14:37 ` Stephen Smalley
2005-03-30 3:41 ` Kodungallur Varma
2005-03-30 12:35 ` Stephen Smalley
2005-04-20 2:09 ` attributes on the other end of a network connection Kodungallur Varma
2005-04-20 3:44 ` James Morris
2005-04-20 12:19 ` Stephen Smalley
2005-05-04 15:30 ` Kodungallur Varma [this message]
2005-05-05 11:28 ` Stephen Smalley
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=fa8ec5d805050408307808096b@mail.gmail.com \
--to=ramgwu@gmail.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.