09.01.2014, 21:35, "Stephen Smalley" <sds@xxxxxxxxxxxxx>: > On 01/09/2014 02:31 PM, Victor Porton wrote: > >> 09.01.2014, 21:25, "Stephen Smalley" <sds@xxxxxxxxxxxxx>: >>> 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: >> AFAIK, there are no support for this in Linux kernel. >> >> It is why I advise to add a new syscall (see my previous message). >>> 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. >> I've already explained some reasons why iptables solution would be wrong. One of the reasons is that this would confuse a system administrator by appearance of new unexpected rules, the automatically added rules would also disappear when iptables script is reloaded, what could make errors for regular users. To use iptables this way seems a really bad idea. > > For SECMARK/CONNSECMARK, there is a separate dedicated security table to > avoid such conflicts. You force me (user) to start some scripts under root. But I want my software to be installable by a regular user in his home directory. It is one reason why adding new syscall into the kernel (see my previous email) would be better than creating such a daemon. Also, I continue to highly doubt that your usage of IP would not interfere with normal system administration. It is also unclear how to implement your daemon. It should create a new kind of "mark" every time a new sandbox binary starts (for two different sandboxes not to interfere with each other). I am not quite sure that this can be implemented in iptables. -- Victor Porton - http://portonvictor.org _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
