Just to let folks know who are attending, we’ve added a lightning talks slot to the LSS 2012 schedule, on Friday 31st August at 2pm.
If you have any emerging topics to discuss, come along on the day and contact me to schedule a slot. We have one confirmed talk already: Dave Jones will be discussing his Trinity system call fuzzing work.
As previously mentioned, LSS this year will be a two-day event, co-located with LinuxCon.
On Day 1, we’re privileged to have a keynote by Matthew Garrett. He’s one of the best speakers in the community, and I believe he’ll be discussing secure boot.
Following the keynote, we have eight refereed presentations on new and interesting Linux security development topics.
On Day 2, we’ll have kernel security subsystem updates from maintainers, followed by an afternoon of breakout sessions. The breakout sessions are for deeper dives into specific areas, and may include development discussions and hack sessions. An BoF is planned to discuss an LF Security Workgroup, and attendees may propose more sessions in the leadup to the conference by emailing the program committee.
Thanks to all of the committee members for reviewing the proposals and helping to organize the summit — it’s shaping up as an interesting and productive event!
As many of you will know, I started a new role at Oracle earlier in the year, going to work on Chris Mason’s team. He announced this week that he’s moving onto a new position at Fusion-io. His leadership at Oracle will be missed, and I would like to congratulate him on his new role.
Also, just to head off the inevitable internet rumours, I thought I’d post here that I will be taking on many of Chris’s previous responsibilities at Oracle, including leading the mainline kernel development team. We’re actively hiring, by the way, so if you want to hack on the Linux kernel for a great company—remotely, from almost anywhere on the planet—email me :-)
Just to let folk know — I’ll be giving a talk on the state of Linux kernel security development at LinuxCon Japan in Yokohama on June 8th. From the abstract:
In this talk, we’ll examine the current state of the Linux kernel security subsystem. Starting with a brief overview of existing features, we’ll discuss recent developments, current efforts and future directions. We’ll also discuss the evolving threat landscape, and the increasing need for mobile and cloud security. This will be a high-level technical discussion aimed at IT professionals. A good general knowledge of operating system and computer security concepts will be advantageous.
I’ll also likely be in Tokyo briefly — if any kernel security development folk there want to meet up, let me know.
This year, the summit will be a two-day event, co-located with LinuxCon, Linux Plumbers, and the Kernel Summit. We’re planning on holding developer break-out sessions for much of the second day, and extending the length of the main talks to the more traditional 45 minute + 15 minute break format. There will still be shorter 30 minute talks, and roundtable discussions.
Check out the programs from previous years to see what kind of proposals have been previously accepted:
I just finished my last day at Red Hat, where I’ve worked as a kernel hacker since 2003. I’ve been fortunate to work with so many brilliant people there on challenging and rewarding projects—like SELinux. If someone had told me in 1999 that Linux would by now be fitted with a mandatory access control system from the NSA, which was enabled by default in major distributions, and certified and deployed in the field, I would have been skeptical. To play a direct role in that would have been a dream come true. It was.
I’ve also had the opportunity to work extensively within the community, during which time I’ve co-maintained or maintained kernel networking, crypto, SELinux and, currently, the security subsystem. This work has taken me around the world and allowed me to make many new friends.
It’s been a great adventure.
Recently, I decided to make some changes in my career path and seek out some new challenges. I’ll be starting in a new role the week after next. I can’t say much about that now, but I will be continuing with my current upstream commitments.