If you’re planning on attending LSS NA in San Diego, note that the Early Bird registration for Open Source Summit (which we’re co-located with) ends today.
You can of course just register for LSS on its own, here.
For 2018, the LSS program committee decided to add a new event in Europe, with the aim of fostering Linux security community engagement beyond North America. There are many Linux security developers and users in Europe who may not be able to obtain funding to travel to North America for the conference each year. The lead organizer and MC for LSS EU is Elena Reshetova, of Intel Finland.
The event overall seemed very successful, with around 150 attendees. We expect to continue now to have both NA and EU LSS events each year, although there are some scheduling challenges for 2019, with several LF events happening closely together. From 2020 on, it seems we will have 4-5 months separation between the EU and NA events, which will work much better for all involved.
Once again, as is typical, the conference was focused around development, somewhat uniquely in the world of security conferences. It’s interesting to see more attention seemingly being paid to the lower parts of the stack: secure booting, firmware, and hardware roots of trust, as well as the continued efforts in hardening the kernel.
Thanks to everyone involved in the event for 2018: the speakers, attendees, the program committee, the sponsors, and the organizing team at the Linux Foundation. LSS-NA would not be possible without all of you!
LSS-NA 2018 will be co-located with the Open Source Summit, and held over 27th-28th August, in Vancouver, Canada. The attendance fee is $100 USD. Register here.
If you’ve been working on a Linux security project, feel welcome to discuss it with the group. We will have a whiteboard and projector. This is also a good opportunity to raise topics for discussion, and to ask questions about Linux security.
LSS will be held this year as two separate events, one in North America
(LSS-NA), and one in Europe (LSS-EU), to facilitate broader participation in
Linux Security development. Note that this CFP is for LSS-NA; a separate CFP
will be announced for LSS-EU in May. We encourage everyone to attend both
events.
LSS-NA 2018 will be held in Vancouver, Canada, co-located with the Open Source Summit.
The CFP closes on June 3rd and the event runs from 27th-28th August.
This is a work in progress to which I’ve been contributing, following on from initial discussions at Linux Plumbers 2017.
In brief, there’s a growing need to be able to provide SELinux confinement within containers: typically, SELinux appears disabled within a container on Fedora-based systems, as a workaround for a lack of container support. Underlying this is a requirement to provide per-namespace SELinux instances, where each container has its own SELinux policy and private kernel SELinux APIs.
A prototype for SELinux namespacing was developed by Stephen Smalley, who released the code via https://github.com/stephensmalley/selinux-kernel/tree/selinuxns. There were and still are many TODO items. I’ve since been working on providing namespacing support to on-disk inode labels, which are represented by security xattrs. See the v0.2 patch post for more details.
Much of this work will be of interest to other LSMs such as Smack, and many architectural and technical issues remain to be solved. For those interested in this work, please see the slides, which include a couple of overflow pages detailing some known but as yet unsolved issues (supplied by Stephen Smalley).
I anticipate discussions on this and related topics (LSM stacking, core namespaces) later in the year at Plumbers and the Linux Security Summit(s), at least.
The session was live streamed — I gather a standalone video will be available soon!
Currently, the agenda includes an update from Kees Cook on the Kernel Self Protection Project, and an update from Jarkko Sakkinen on TPM support. I’ll provide a summary of the recent Linux Security Summit, depending on available time, perhaps focusing on security namespacing issues.
This agenda is subject to change and if you have any topics to propose, please send an email to the ksummit-discuss list.