New Blog on how SELinux blocked Docker container escape.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: SELinux <selinux@xxxxxxxxxxxxx>, Fedora SELinux Users <selinux@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: New Blog on how SELinux blocked Docker container escape.
From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
Date: Fri, 13 Jan 2017 14:48:20 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0

http://rhelblog.redhat.com/2017/01/13/docker-0-day-stopped-cold-by-selinux/

_______________________________________________
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.

Follow-Ups:
- Re: New Blog on how SELinux blocked Docker container escape.
  - From: Tracy Reed
- Re: New Blog on how SELinux blocked Docker container escape.
  - From: Dominick Grift

Prev by Date: Re: [PATCH] policy_define.c: don't free memory returned from queue_head()
Next by Date: Re: [PATCH] restorecon manpage: link back to fixfiles
Previous by thread: [PATCH] policy_define.c: don't free memory returned from queue_head()
Next by thread: Re: New Blog on how SELinux blocked Docker container escape.
Index(es):
- Date
- Thread

[Index of Archives] [Selinux Refpolicy] [Linux SGX] [Fedora Users] [Fedora Desktop] [Yosemite Photos] [Yosemite Camping] [Yosemite Campsites] [KDE Users] [Gnome Users]

Powered by Linux