Paul Moore (@[email protected])

Linux Kernel developer who likes playing with security things. I can also be found at @[email protected]

[Paul Moore (@[email protected]) @securepaul]

Since it worked well with the Linux v6.5 merge window, here are my notes on the SELinux and audit kernel changes that went into Linus' tree for the upcoming Linux v6.6 release:

https://t.co/TtmJjqDQLn

#selinux #audit

[Paul Moore (@[email protected]) @securepaul]

Brett Anderson recently contributed another cool looking SELinux logo to the community. You can find it in the selinux artwork repository on GitHub.

https://t.co/kueb1pAxbk

https://t.co/7rnfe6AMT7

#selinux

[Paul Moore (@[email protected]) @securepaul]

On August 8, 2003 Linux v2.6.0-test3 was released and included the first release of SELinux in an upstream Linux kernel. Happy 20th birthday SELinux!

https://t.co/g7GUX9yilt

#selinux

[Paul Moore (@[email protected]) @securepaul]

Ten years ago today, Android 4.3 (Jelly Bean) was released, the first Android release to support SELinux. Happy birthday SEAndroid!

https://t.co/h83tRmeXaW

#selinux #android

[Paul Moore (@[email protected]) @securepaul]

@love_reading50 SELinux is a community led project, the long term vision for the project is based on what the community members contribute.

[Paul Moore (@[email protected]) @securepaul]

It was recently suggested that my SELinux and audit kernel highlights might be more useful during the merge window. With that in mind, here are the highlights from the SELinux and audit pull requests for Linux v6.5:

https://t.co/HaNjjEXvBa

#selinux #audit

[Paul Moore (@[email protected]) @securepaul]

Linux v6.4 was released on Sunday and while there are no audit updates worth mentioning, there were some significant SELinux changes:

https://t.co/e00YTGZrLe

#selinux

[Paul Moore (@[email protected]) @securepaul]

Some administrative updates to the SELinux Project repositories hosted on GitHub.

https://t.co/Pl5i7WTkrg

#selinux

[Paul Moore (@[email protected]) @securepaul]

@Masmullin1 That's a good question, but a dangerous one too. We've always tried to avoid discussions about implementing one LSM's security model in another as it gets very nasty. See some of the early discussions around SELinux vs AppArmor, SELinux vs Smack, etc.

[Paul Moore (@[email protected]) @securepaul]

Next week I'll be moderating a panel of LSM maintainers, if you could ask them a question, what would you ask?

#lssna #linux #security

https://t.co/egpKxwuoXu

[Paul Moore (@[email protected]) @securepaul]

Linux v6.3 was released on Sunday and brought a small handful of #SELinux and audit changes.

https://t.co/1oRLpns5sR

[Paul Moore (@[email protected]) @securepaul]

New release of #selinux userspace today:

https://t.co/UudEr0AQSF

[Paul Moore (@[email protected]) @securepaul]

Linux v6.2 wasn't a very big release from a #selinux or #audit perspective, but here are the highlights:

https://t.co/H24mHWNL0o

[Mickaël Salaün @l0kod]

For @outreachy applicants willing to work on Linux kernel and security, @securepaul and myself will mentor this project: Improve Landlock tests and thread management
https://t.co/Nfcig7IBmO

[Mickaël Salaün @l0kod]

I'll give a talk tomorrow at #FOSDEM in the #rustlang dev room about "Backward and forward compatibility for security features" (illustrated with #Landlock)
https://t.co/gT4HXsKEng

[Christian Brauner @brau_ner]

Very happy to have my #MSFT colleague @ztfasr giving a talk in the #Kernel #Devroom at #FOSDEM23 next week! :)

[Paul Moore (@[email protected]) @securepaul]

A new release of The SELinux Notebook is out, with PDF and EPUB versions available to download.

https://t.co/NFJI7KH57F

[Paul Moore (@[email protected]) @securepaul]

SELinux and audit highlights for Linux v6.1

https://t.co/HnqrDPeBOp

[Chris PeBenito @pebenito]

Announcing SELinux Reference policy 3 pre-alpha!

SELinux Reference Policy 3 is a rewrite using the Cascade policy language.

https://t.co/4isV3FE434

See https://t.co/BoxreIJTM0 for announcement.

[Paul Moore (@[email protected]) @securepaul]

Today seems like a good day to mention that you can also find me at @[email protected]

I'm not active there at the moment, but I suspect that might change fairly quickly.