In previous years, attending the Linux Security Summit (LSS) has required full registration as a LinuxCon attendee. This year, LSS has been upgraded to a hosted event. I didn’t realize that this meant that LSS registration was available entirely standalone. To quote an email thread:
If you are only planning on attending the The Linux Security Summit, there is no need to register for LinuxCon North America. That being said you will not have access to any of the booths, keynotes, breakout sessions, or breaks that come with the LinuxCon North America registration. You will only have access to The Linux Security Summit.
Thus, if you wish to attend only LSS, then you may register for that alone, at no cost.
There may be a number of people who registered for LinuxCon but who only wanted to attend LSS. In that case, please contact the program committee at lss-pc_AT_lists.linuxfoundation.org.
CC3: An Identity Attested Linux Security Supervisor Architecture – Greg Wettstein, IDfusion
SELinux in Android Lollipop and Android M – Stephen Smalley, NSA
Linux Incident Response – Mike Scutt and Tim Stiller, Rapid7
Assembling Secure OS Images – Elena Reshetova, Intel
Linux and Mobile Device Encryption – Paul Lawrence and Mike Halcrow, Google
Security Framework for Constraining Application Privileges – Lukasz Wojciechowski, Samsung
IMA/EVM: Real Applications for Embedded Networking Systems – Petko Manolov, Konsulko Group, and Mark Baushke, Juniper Networks
Ioctl Command Whitelisting in SELinux – Jeffrey Vander Stoep, Google
IMA/EVM on Android Device – Dmitry Kasatkin, Huawei Technologies
There will be several discussion sessions:
Core Infrastructure Initiative – Emily Ratliff, Linux Foundation
Linux Security Module Stacking Next Steps – Casey Schaufler, Intel
Discussion: Rethinking Audit – Paul Moore, Red Hat
Also featured are brief updates on kernel security subsystems, including SELinux, Smack, AppArmor, Integrity, Capabilities, and Seccomp.
The keynote speaker will be Konstantin Ryabitsev, sysadmin for kernel.org. Check out his Reddit AMA!
See the schedule for full details, and any updates.
This year’s summit will take place on the 20th and 21st of August, in Seattle, USA, as a LinuxCon co-located event. As such, all Linux Security Summit attendees must be registered for LinuxCon. Attendees are welcome to attend the Weds 19th August reception. ETA: standalone LSS registration is available.
The regular LWN kernel development stats have been posted here for version 4.1 (if you really don’t have a subscription, email me for a free link). In this, Jon Corbet notes:
over 60% of the changes going into this kernel passed through the hands of developers working for just five companies. This concentration reflects a simple fact: while many companies are willing to support developers working on specific tasks, the number of companies supporting subsystem maintainers is far smaller. Subsystem maintainership is also, increasingly, not a job for volunteer developers..
As most folks reading this would know, I lead the mainline Linux Kernel team at Oracle. We do have several people on the team who work in leadership roles in the kernel community (myself included), and what I’d like to make clear is that we are actively looking to support more such folk.
If you’re a subsystem maintainer (or acting in a comparable leadership role), please always feel free to contact me directly via email to discuss employment possibilities. You can also contact Oracle kernel folk who may be presenting or attending Linux conferences.
All LSS attendees, including speakers, must be registered attendees of LinuxCon. The first round of early registration ends May 29th.
We’d like to cast our net as wide as possible in terms of presentations, so please share this info with anyone you know who’s been doing interesting Linux security development or implementation work recently.
We had an engaging and productive two days, with strong attendance throughout. We’ll likely follow a similar format next year at LinuxCon. I hope we can continue to expand the contributor base beyond mostly kernel developers. We’re doing ok, but can certainly do better. We’ll also look at finding a sponsor for food next year.
The event will be held over two days (18th & 19th August), starting with James Bottomley as the keynote speaker. The keynote will be followed by referred talks, group discussions, kernel security subsystem updates, and break-out sessions.
The refereed talks are:
Verified Component Firmware – Kees Cook, Google
Protecting the Android TCB with SELinux – Stephen Smalley, NSA
Tizen, Security and the Internet of Things – Casey Schaufler, Intel
Capsicum on Linux – David Drysdale, Google
Quantifying and Reducing the Kernel Attack Surface – Anil Kurmus, IBM
Extending the Linux Integrity Subsystem for TCB Protection – David Safford & Mimi Zohar, IBM
Application Confinement with User Namespaces – Serge Hallyn & Stéphane Graber, Canonical
Discussion session topics include Trusted Kernel Lock-down Patch Series, led by Kees Cook; and EXT4 Encryption, led by Michael Halcrow & Ted Ts’o. There’ll be kernel security subsystem updates from the SELinux, AppArmor, Smack, and Integrity maintainers. The break-out sessions are open format and a good opportunity to collaborate face-to-face on outstanding or emerging issues.
The CFP for the 2014 Linux Security Summit is announced.
LSS 2014 will be co-located with LinuxCon North America in Chicago, on the 18th and 19th of August. We’ll also be co-located with the Kernel Summit this year.
Note that, as always, we’re looking for participation from the general Linux community — not just kernel people, and not just developers. We’re interested in hearing about feedback from users, and discussing what kinds of security problems we need to be addressing into the future.
This year, we’re looking for discussion topics as well as paper presentations, so if you have anything interesting to talk about, send in a proposal.