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
In Fedora 6 and Red Hat Enterprise Linux 5 we introduced setroubleshoot. This is a tool which listens for AVC audit messages and then runs them through a database of plugins looking for a match, and then trying to explain what SELinux has prevented and how to fix the problem or to react to a potential break in. It has been fairly successful in explaining what SELinux is doing. Most people that
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く