From: Stephen Smalley <sds@tycho.nsa.gov>
To: Victor Porton <porton@narod.ru>, selinux@tycho.nsa.gov
Subject: Re: Restrict to a fixed Internet domain in a sandbox
Date: Thu, 09 Jan 2014 14:25:08 -0500 [thread overview]
Message-ID: <52CEF794.3030501@tycho.nsa.gov> (raw)
In-Reply-To: <23731389285461@web11j.yandex.ru>
On 01/09/2014 11:37 AM, Victor Porton wrote:
> I remind that sandbox is implemented in Fedora using SELinux.
>
> It would be useful to restrict sandboxed application to connect only to one, programmatically specified Internet domain (just like Java and JavaScript security).
>
> It seems it is impossible with current SELinux.
>
> Could you add necessary features? Please!
I'm not aware of any missing kernel features required to support your
functionality. I think all you are missing is two userspace components:
a library that provides whatever interface you design, and a daemon
that receives the specification in whatever form you design and turns it
into a set of SELinux and iptables SECMARK/CONNSECMARK rules to label
the packets so that SELinux can mediate them accordingly, and loads that
into the kernel for enforcement.
next prev parent reply other threads:[~2014-01-09 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 16:37 Restrict to a fixed Internet domain in a sandbox Victor Porton
2014-01-09 16:59 ` Victor Porton
2014-01-09 17:03 ` William Roberts
2014-01-09 17:19 ` Victor Porton
2014-01-09 17:34 ` William Roberts
2014-01-09 18:28 ` Victor Porton
2014-01-09 18:59 ` Victor Porton
2014-01-09 19:18 ` Victor Porton
2014-01-09 19:22 ` Victor Porton
2014-01-09 19:25 ` Stephen Smalley [this message]
2014-01-09 19:31 ` Victor Porton
2014-01-09 19:34 ` Stephen Smalley
2014-01-09 19:44 ` Victor Porton
2014-01-09 19:58 ` Victor Porton
2014-01-09 20:06 ` Stephen Smalley
2014-01-09 20:14 ` Victor Porton
2014-01-09 20:21 ` Stephen Smalley
2014-01-10 18:41 ` Victor Porton
2014-01-10 18:47 ` Stephen Smalley
2014-01-10 18:53 ` Victor Porton
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=52CEF794.3030501@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=porton@narod.ru \
--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.