16:29:39 #startmeeting fedora_coreos_meeting 16:29:39 Meeting started Wed Nov 2 16:29:39 2022 UTC. 16:29:39 This meeting is logged and archived in a public location. 16:29:39 The chair is dustymabe. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:29:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:29:39 The meeting name has been set to 'fedora_coreos_meeting' 16:29:43 #topic roll call 16:30:05 .hello2 16:30:06 jdoss: jdoss 'Joe Doss' 16:30:07 .hello jasonbrooks 16:30:08 .hi 16:30:09 jbrooks: jasonbrooks 'Jason Brooks' 16:30:12 gursewak: gursewak 'Gursewak Singh' 16:30:38 .hello2 16:30:39 jlebon: jlebon 'None' 16:30:44 Hi all! 16:31:08 .hi 16:31:09 lucab: lucab 'Luca BRUNO' 16:31:14 .hi 16:31:15 dustymabe: dustymabe 'Dusty Mabe' 16:31:23 .hi 16:31:25 fifofonix: fifofonix 'Fifo Phonics' 16:31:31 #chair jdoss jbrooks gursewak jlebon c4rt0 lucab fifofonix 16:31:31 Current chairs: c4rt0 dustymabe fifofonix gursewak jbrooks jdoss jlebon lucab 16:31:47 .hi 16:31:48 c4rt0: c4rt0 'Adam Piasecki' 16:31:54 .hi 16:31:55 bgilbert: bgilbert 'Benjamin Gilbert' 16:32:17 #chair bgilbert 16:32:17 Current chairs: bgilbert c4rt0 dustymabe fifofonix gursewak jbrooks jdoss jlebon lucab 16:33:12 #topic Action items from last meeting 16:33:23 This is all we had in the list: 16:33:26 * bgilbert will follow up on https://github.com/coreos/fedora-coreos-tracker/issues/567 re. VMware 16:33:35 done 16:34:05 #info bgilbert addressed VMWare concerns in https://github.com/coreos/fedora-coreos-tracker/issues/567#issuecomment-1294655290 16:34:43 .hello copperi 16:34:43 copperi[m]: copperi 'Jan Kuparinen' 16:34:44 .hi 16:34:46 jmarrero: jmarrero 'Joseph Marrero' 16:34:50 ok we're a bit light on topics but we have some security ones to FYI at least 16:35:01 #chair copperi[m] jmarrero 16:35:01 Current chairs: bgilbert c4rt0 copperi[m] dustymabe fifofonix gursewak jbrooks jdoss jlebon jmarrero lucab 16:35:10 #topic Update OpenSSL for CVE-2022-3786 and CVE-2022-3602 16:35:16 #link https://github.com/coreos/fedora-coreos-tracker/issues/1329 16:35:53 #info the `testing` and `next` streams have a fix for the OpenSSL CVEs - `stable` will roll out later today 16:36:19 I haven't heard or seen any issues related to the updates? has anyone else? 16:36:38 haven't either 16:36:46 Nothing 16:36:51 ack 16:37:05 i'll move on to the next topic 16:37:22 #topic Non-default OSTree deployments accessible without GRUB password (CVE-2022-3675) 16:37:28 #link https://github.com/coreos/fedora-coreos-tracker/issues/1333 16:37:57 jlebon maybe? 16:38:31 This was a new security issue related to FCOS - it was made public yesterday. 16:38:49 or I can take it 16:38:57 bgilbert: feel free :) 16:39:00 The announcement with relevant information is at https://discussion.fedoraproject.org/t/non-default-ostree-deployments-accessible-without-grub-password-cve-2022-3675/43715 16:39:09 you did most of the work there 16:39:19 jlebon found it :-) 16:39:33 the relates to the recently-added GRUB password support 16:39:38 is this a smelt it you dealt it kind of thing? 16:39:48 jdoss: just trying to give credit :-P 16:39:55 hahah fair enough 16:40:12 if you enable a GRUB password with Butane, GRUB is supposed to prevent anyone at the GRUB console from: 16:40:43 getting to the GRUB command line, modifying menu entries (including changing kernel arguments), or booting deployments other than the latest 16:40:49 ...without entering a password. 16:41:31 we had a regression in the "booting old deployments" part 16:42:12 machines are affected based on the FCOS version they were _installed_ from, not the version they're currently running 16:42:42 so for a couple months, new installs with GRUB passwords would allow old deployments to be booted. 16:43:54 this isn't a major vulnerability, but we got a CVE number for it because it is a small one: it allows an unprivileged person with access to the console at boot time to boot into an older OS release, potentially reverting security updates from the latest release. 16:44:21 for anyone who's especially concerned about this, the announcement has manual steps for closing the hole immediately 16:44:33 👍 16:44:42 otherwise, today's releases will stop introducing the hole for new installs 16:44:49 thanks bgilbert and jlebon for working to close that hole 16:44:56 for existing installs, we're rolling out an automatic fix for affected nodes, on the normal release schedule 16:45:26 i.e., today's next and testing releases will fix existing machines on those streams, and the subsequent stable release in two weeks will fix existing stable machines 16:46:31 thanks again to jlebon for finding this, and thanks to dustymabe and jlebon for helping coordinate the fix alongside the F37 rebase and the OpenSSL fix <3 16:46:46 any questions/concerns? 16:46:48 exciting times in FCOS release coordination 16:46:51 :) 16:47:38 thank you for the context and info bgilbert 16:48:14 i think the biggest takeaway for me is we need to be more thorough on test coverage 16:48:24 #info please see the announcement for more context on the nature of the security issue and the release fix schedule: https://discussion.fedoraproject.org/t/non-default-ostree-deployments-accessible-without-grub-password-cve-2022-3675/43715 16:48:25 especially for security features 16:49:08 +1 jlebon 16:50:14 ok the remaining issues tagged with meeting - one of them is for travier to introduce and I don't think he is here today and the other one is kind of a reminder that we need to work on a few tasks to unblock ppc64le 16:50:29 i propose we go straight to open floor (unless any other topics are worth bringing up standalone) 16:50:41 Sorry for being late (catching up) 16:50:49 #chair spresti[m] 16:50:49 Current chairs: bgilbert c4rt0 copperi[m] dustymabe fifofonix gursewak jbrooks jdoss jlebon jmarrero lucab spresti[m] 16:51:26 SGTM 16:51:47 #topic open floor 16:51:56 anybody with any topics for open floor? 16:52:16 If you have not tried the layered container stuff. Give it a shot. I am loving it! 16:52:52 nice 16:52:55 (would love to see a youtube walkthrough or similar of that container layering stuff) 16:53:26 I think jmarrero is going to talk about it a bit at the fedora release party coming up (is that this Friday?) 16:53:32 I gave an internal demo to my eng team about shipping our app in a container layer and it was well received. 16:53:48 Yeah this Friiday, hopefully with enough time for a quick demo. 16:54:14 i'll note we discovered an issue where `next` nodes currently are using recompiled selinux policies OOTB 16:54:21 #link https://github.com/openshift/os/issues/1036#issuecomment-1299168792 16:54:30 jdoss: so let me get this right.. your higher level application is no longer running as a container but as software delivered via "layering"? 16:54:44 it doesn't affect stable and testing yet, and we're working on working around it before it gets there 16:55:16 I am shipping container tarballs of our multi service app in one big FCOS layer. 16:55:58 but how is it run once the system is up? via podman, or directly on the host? 16:56:01 What are "container tarballs" in this context? 16:56:06 and using systemd to launch everything. We are using podman (kube play) to pull the stuff out of our SaaS k8s and translating it to systemd units with Podman. 16:56:48 jlebon++ 16:56:57 I will push up my demo repo and post it in #fedora-coreos this week. I demo'ed using Paperless NGX as the app getting shipped. 16:57:32 OK, we actually are building up some support for embedding stock container images inside ostree commits, see https://github.com/ostreedev/ostree/pull/2717 16:57:42 jdoss: cool. Yeah the reason I ask the question is I'm trying to make sure users still run their applications in containers 16:58:13 100% we have every service in a container running in a Podman pod. 16:58:17 perfect 16:58:43 (I'm trying to not create a hard barrier, but rather a spectrum of flexible tools) 16:59:04 we are just using the FCOS container layer to version everything https://quay.io/repository/quickvm/paperless-ngx?tab=tags 16:59:30 I can explain more in #fedora-coreos when I get the repo pushed up. 16:59:39 any other topics for open floor 16:59:58 perhaps we should advertise the FCOS agenda item on release party to the fedoracoreos list? but i''m going to try and make it now i know about it! 17:00:28 yeah - maybe at least a discussion forum post and maybe a tweet 17:01:13 any other topics for open floor? 17:01:30 byeeeeeeeee 17:01:37 Thanks dusty for running the meeting 17:01:42 #endmeeting