The other day some of my colleagues and I were discussing a recent request for the Linux Kernel to add "security sandbox" functionality. We talked about how we could do this with SELinux. The discussions brought up an old Bug report of my about writing policy for the "little things". SELinux does a great job of confining System Services, but what about applications executed by users.  The bug r
第2å SELinuxã§ããããããã¯ã¢ããï¼ãªã¹ãã¢ãã¦ã¿ã é¢ åæ¯ ãµã¤ãªã¹ãã¯ããã¸ã¼æ ªå¼ä¼ç¤¾ OSSãã¯ããã¸ã¼ã»ã³ã¿ã¼ éçºæ¯æ´ã°ã«ã¼ã ã°ã«ã¼ãããã¼ã¸ã£ã¼ 2007/6/20 ä»åã¯ãååã»ããã¢ããããPloneï¼Zopeã®ã³ã³ãã³ã管çã·ã¹ãã ãåºã«ãSELinuxãæå¹ã«ããå ´åã®ããã¯ã¢ããã«é¢ãã¦èå¯ãã¦ã¿ã¾ããããå¼ãç¶ããååä½æããCentOS 4.4ï¼Ploneç¨ã«ã«ã¹ã¿ãã¤ãºããSELinuxãç¨ãã¾ãã SELinuxã®ããã¯ã¢ããã«ãã ããçç± ããã¯ã¢ããï¼ãªã¹ãã¢ã¯Linuxéç¨ã®åºç¤ã®åºç¤ã§ã¯ï¼ ã¨æãããããããã¾ãããããã¦SELinuxã®ããã¯ã¢ããã«ãã ãã£ãçç±ã¯ãSELinuxã«ã¯ãã¡ã¤ã«ã·ã¹ãã ä¸ã§ãæ¡å¼µå±æ§ï¼XATTRï¼ãæ å ±ãæã¤ã¨ããç¹å¾´ãããããã§ãã å¾ã£ã¦å®éã«éç¨ãã¦ããããã§ã¯ãå種ããã¯ã¢ããããã°ã©ã ã«ãã£ã¦å
[evil@gateway.example.com ~] $ ssh [email protected] root:$1$d8kgaeX7$PqJEIeNsGAGPw4WwiVy0C/:14217:0:99999:7::: bin:*:14189:0:99999:7::: daemon:*:14189:0:99999:7::: adm:*:14189:0:99999:7::: lp:*:14189:0:99999:7::: sync:*:14189:0:99999:7::: shutdown:*:14189:0:99999:7::: halt:*:14189:0:99999:7::: mail:*:14189:0:99999:7::: news:*:14189:0:99999:7::: uucp:*:14189:0:99999:7::: operator:*:14189:0:9
Overview sVirt is a community project which integrates Mandatory Access Control (MAC) security and Linux-based virtualization (KVM, lguest et al). sVirt was created by James Morris Resources Presentations "sVirt: Hardening Linux Virtualization with Mandatory Access Control" presented at linux.conf.au 2009 Code drops v0.10 v0.20 v0.30 Now merged into upstream libvirt. Requirements analysis v1.0 Pro
ãç¥ãã
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}