security-sig
LOGS
<@q5sys:matrix.org>
14:59:51
!startmeeting
<@meetbot:fedora.im>
14:59:55
Meeting started at 2026-08-13 14:59:51 UTC
<@meetbot:fedora.im>
14:59:55
The Meeting name is 'Fedora Meeting 3'
<@q5sys:matrix.org>
14:59:57
!meetingname security-sig
<@meetbot:fedora.im>
15:00:22
The Meeting Name is now security-sig
<@q5sys:matrix.org>
15:00:23
<@q5sys:matrix.org>
15:00:27
<@py0xc3:fedora.im>
15:00:29
!hi
<@q5sys:matrix.org>
15:00:30
!info Open floor to discuss anything security related. (2026-08-13)
<@q5sys:matrix.org>
15:00:31
!info Next Meeting (2026-08-20)
<@q5sys:matrix.org>
15:00:32
!info There are 12 open tickets in the main Security Forge: https://forge.fedoraproject.org/security/tickets/issues
<@q5sys:matrix.org>
15:00:35
!info There are 5 open tickets in the Security Docs Forge: https://forge.fedoraproject.org/security/docs/issues
<@q5sys:matrix.org>
15:00:37
!topic Agenda: https://discussion.fedoraproject.org/t/agenda-for-the-security-sig-meeting-on-6th-august-2026/198486
<@q5sys:matrix.org>
15:00:38
Since the Agenda is open, this is an open floor.
<@thebeanogamer:fedora.im>
15:01:54
!hi
<@zodbot:fedora.im>
15:01:55
Daniel Milnes: Daniel Milnes (thebeanogamer) - he / him / his
<@py0xc3:fedora.im>
15:02:01
!hi
<@zodbot:fedora.im>
15:02:02
Chris (py0xc3): Christopher Klooz (py0xc3) - he / him / his
<@thebeanogamer:fedora.im>
15:02:03
Though tbh I’ve got nothing for this week
<@py0xc3:fedora.im>
15:02:13
me neither ;)
<@natsucamellia:fedora.im>
15:02:17
!hi
<@zodbot:fedora.im>
15:02:18
Jeffrey Wang: Jeffrey Wang (natsucamellia) - he / him / his
<@py0xc3:fedora.im>
15:02:32
Hi Jeffrey 👋
<@natsucamellia:fedora.im>
15:02:59
So many thing popped up, don't know what's going on 😆
<@q5sys:matrix.org>
15:05:24
I dont either, but Im here in case someone wanders in with a question
<@natsucamellia:fedora.im>
15:06:14
typically, what do you discuss in a meeting?
<@py0xc3:fedora.im>
15:07:05
Whatever is on the agenda :) You can review the earlier agendas https://forge.fedoraproject.org/security/tickets/commits/branch/main/agenda-next.md
<@q5sys:matrix.org>
15:07:28
The past few meeting agendas are here, https://discussion.fedoraproject.org/tag/security-sig/1053
<@py0xc3:fedora.im>
15:07:54
Or on discourse, that might be easier -> https://discussion.fedoraproject.org/tag/security-sig/1053
<@py0xc3:fedora.im>
15:08:05
Same thought :D
<@jforbes:fedora.im>
15:08:09
!hi
<@zodbot:fedora.im>
15:08:12
jforbes: Justin Forbes (jforbes) - he / him / his
<@jforbes:fedora.im>
15:09:02
Typical rules apply, ping me if you need me. I try to follow, but also in another meeting and can miss things
<@py0xc3:fedora.im>
15:10:36
No worries, there is no agenda today :) So we all can relax.
<@py0xc3:fedora.im>
15:11:16
The same for me, if anyone needs something from me, let me know. Otherwise, I cannot exclude I focus on something else and miss to follow ^^
<@natsucamellia:fedora.im>
15:13:23
What kind of contributions do you make to Fedora? Security patches or something else?
<@jforbes:fedora.im>
15:14:30
Who specifically are you asking?
<@natsucamellia:fedora.im>
15:15:05
everyone! I'm curious about this team
<@jforbes:fedora.im>
15:15:32
I am the kernel maintainer, though also packaging module jail, hope to push up for review next week.
<@salimma:fedora.im>
15:15:38
!hi
<@zodbot:fedora.im>
15:15:40
Michel Lind ☘ UTC+1: Michel Lind (salimma) - he / him / his
<@salimma:fedora.im>
15:16:01
sorry folks, finishing up some changes to my lag analysis tool and didn't notice the time
<@jforbes:fedora.im>
15:16:17
Also proven packager, so I can patch things that need it if the maintainer is unresponsive or away
<@natsucamellia:fedora.im>
15:17:07
wow
<@q5sys:matrix.org>
15:17:38
I'm a spin maintainer; Fedora Security Lab, Fedora Jam, Fedora Astonomy, Fedora Games Lab, and Fedora Scientific Lab
<@natsucamellia:fedora.im>
15:19:10
Do Fedora maintain its own kernel, or just use the mainline kernel?
<@jforbes:fedora.im>
15:20:58
We are currently carrying ~100 patches that are not in mainline, but by policy we try to keep as close to mainline as possible
<@natsucamellia:fedora.im>
15:21:10
I didn't know there are so many spins, interesting
<@natsucamellia:fedora.im>
15:23:04
So eventually the patches will be merged into mainline right? If the mainline accepts them.
<@jforbes:fedora.im>
15:25:00
There are some exceptions, like Linus has rejected the thing that turns on lockdown if Secure Boot is turned on in EFI. But yes, most things are headed upstream. Many currently are already upstream, but not in stable trees yet
<@natsucamellia:fedora.im>
15:25:33
I found it
<@natsucamellia:fedora.im>
15:26:09
It's so amazing that the maintainer is here
<@salimma:fedora.im>
15:27:54
oh I see we're doing intros
<@salimma:fedora.im>
15:27:54
<@salimma:fedora.im>
15:27:54
I'm on the Engineering Steering Committee and its Packaging subcommittee, and on the KDE working group (and used to be on Workstation) as well as Rust, Python, and Golang SIGs (and Lua but that one is not fully up to speed yet)
<@salimma:fedora.im>
15:27:54
<@salimma:fedora.im>
15:27:54
and a provenpackager
<@jforbes:fedora.im>
15:28:07
I try to be pretty accessible. But also a lot of critical security ends up in kernel. So it makes sense
<@jforbes:fedora.im>
15:29:48
Of note to folks, I talked to the upstream maintainer of Module Jail ( https://modulejail.com/ ). I am going to maintain the Fedora package and get it into proper repos. I don't think we will ever turn it on by default, but it will be an option
<@salimma:fedora.im>
15:30:31
oh that sounds interesting
<@natsucamellia:fedora.im>
15:31:37
really interesting project
<@jforbes:fedora.im>
15:31:37
It will mitigate a lot of the these security issues that we see for many users. It doesn't change the landscape for people running scanners for audits, because scanners see a "bad" module on the system and don't grok that it has been blacklisted. But compliance vs practical security are often 2 different things
<@jforbes:fedora.im>
15:32:50
I *think* I have someone willing to do the epel builds for it as well.
<@jforbes:fedora.im>
15:33:31
Well, I can do the builds, but wanted someone who actually has RHEL somewhere willing to take epel bugs.
<@py0xc3:fedora.im>
15:37:52
Don't think that can be finalized within the meeting, but that is worth a ticket I think.
<@jforbes:fedora.im>
15:38:11
Oh, I have someone I think
<@jforbes:fedora.im>
15:38:43
Doesn't really need a ticket. I am kind of trying to get someone internal in hopes that it actually becomes a part of RHEL 11 when it branches... But no promises on that
<@py0xc3:fedora.im>
15:48:50
If no one has points, we might end the meeting? ~50 minutes by now
<@q5sys:matrix.org>
15:48:59
I was just typing that out... haha
<@py0xc3:fedora.im>
15:49:07
I read your mind :P
<@q5sys:matrix.org>
15:49:08
ive got to run for another meeting, so I'm going to go ahead and call the meeting here. Since its an open floor, it's not like im cutting off a topic.
<@q5sys:matrix.org>
15:49:28
!endmeeting
<@py0xc3:fedora.im>
15:49:31
Sure. See you in the channel everybdoy