Thursday, 2021-11-04

gagehugo#startmeeting security15:01
opendevmeetMeeting started Thu Nov  4 15:01:09 2021 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'security'15:01
gagehugoo/15:01
fungiahoy!15:01
gagehugo#link https://etherpad.opendev.org/p/security-agenda agenda15:01
gagehugo#topic PTG recap15:04
gagehugo#link https://etherpad.opendev.org/p/security-sig-ptg-yoga15:04
gagehugoNotes from the PTG15:04
fungiwe didn't get around to talking through the list of repos did we?15:07
fungioh, right, i was having problems with my computer locking up15:08
gagehugoyeah haha15:08
gagehugoWe can talk about it today though15:08
fungiturns out it's something specific to the i915 kernel driver and intel internal video chipsets when running on battery15:08
gagehugohmm15:09
gagehugothat is a bit specific15:09
fungii was trying to run on battery because the usb headset i've got has really poor electrical isolation and the mic picks up a 60hz hum whenever i plug in a type-c charger15:09
fungiyeah, someone reported a similar problem to debian-devel later that week and i realized it was only happening when i was on battery15:10
fungionce i thought back15:10
gagehugointeresting15:10
fungianyway, not at all security related, just was a surprising discovery15:10
gagehugoMy previous DAC on my desktop liked to pickup some noise whenever someone texted me and my phone was nearby on the desk15:11
fungioh, yeah i've had that, though mostly just with fm radios15:12
gagehugoheh15:12
gagehugo#topic retiring git repos15:12
gagehugo#link https://opendev.org/openstack/governance/src/commit/0f0b0ce7d99188447a1fabcbc3165c4305815066/reference/sigs-repos.yaml#L76-L8015:12
fungiso looking through those, we definitely still use ossa15:13
fungii'm rather certain we can retire security-specs15:14
gagehugoDo we still use security-analysis with the latest changes to the vulnerability:managed tagging?15:14
gagehugoactually the only projects in that repo docs are barbican and KSM15:15
fungiwe recommend that projects undergo a security analysis, but honestly i've always felt that having it in a separate repository makes little sense, it would be more useful for those to exist in the project docs15:15
fungiit was in its own repo originally because we recommended that the projects seek out independent reviews of their analyses, but that was all based around the ossg acting as reviewers for them15:16
gagehugoyeah15:16
gagehugowe tried to get several of the keystone libraries covered in the past with the process before it all changed15:17
fungithe other repo there is security-doc which does need some love but gets updates from time to time15:18
fungithough with no tech writing sig any longer, it will most likely be on us to do any reviewing there if we keep it15:18
gagehugomakes sense15:19
fungiagain, it may make more sense for security recommendations to go into project documentation anyway?15:19
fungithat's worth bringing up on the ml probably15:19
gagehugosure15:19
gagehugoinstead of having it all over the place15:20
fungiwell, it's more that project install docs are most likely how people are finding out how to do installations (or they're using a canned installer/distro)15:23
gagehugoyeah, installations/configurations15:23
fungiand we're expecting them to go to some separate document if they're one of those weird people who actually wants a secure deployment15:24
gagehugohah15:24
fungimuch better if openstack is secure by default, recommending secure options in the install docs15:24
gagehugobut yeah it makes sense to just have that info in the same place15:24
fungias for repos reporting into this channel with gerritbot, looks like it's the same 4 as in the sigs-repos list for us15:27
fungiso the idea is to retire security-specs (it hasn't had a spec change in 6 years), propose moving security-analysis and security-doc into project docs, keep ossa15:29
gagehugoI am fine with that15:30
fungimoving security-analysis and security-doc *content* into project docs, i mean, and then retire them (keeping the old versions published i guess for the sake of old hyperlinks)15:31
gagehugoyes15:31
fungiokay, i can start an ml thread about security-analysis and security-doc i suppose, unless you're keen to take that15:32
gagehugoThat works15:32
fungisecurity-specs we can clearly just retire, that doesn't need further discussion as far as i can see15:32
gagehugoI can retire that repo then15:32
fungithanks!15:34
gagehugo#topic open discussion15:34
gagehugoI don't have anything else for this meeting15:35
fungiit's not visible work, but i've been following up with ptls and security liaisons on old private bugs for deliverables the vmt doesn't officially oversee, trying to get them cleaned up where possible15:35
gagehugooh nice!15:36
fungiyeah, mainly just trying to make sure things don't fall through the cracks15:36
gagehugosounds good15:37
fungii'm okay with public security reports falling stale, someone can always find them and decide to work on them, but the private ones are at risk of rotting without ever seeing the light of day15:37
gagehugoyeah, that's a good point15:37
fungifor vmt-overseen deliverables that's not a problem these days because we have a maximum embargo period those projects have agreed to15:38
gagehugoyeah, that definitely helps move things along eventually15:39
fungioh, before i forget, i also discovered recently that there's an update we should probably make to our embargoed disclosure process15:39
fungi#link https://oss-security.openwall.org/wiki/mailing-lists/distros15:40
fungiunder the "List policy and instructions for reporters" section there are a couple of things we haven't been doing when sending to the provate linux-distros ml as a downstream stakeholder15:41
fungis/provate/private/15:41
fungiin particular, including "[vs]" in the subject, and encrypting the message body for the key included there15:42
fungiit dawned on me recently when i got a reply from one of the volunteers to linux-distros, which was encrypted to my openpgp key, that they probably expected me to encrypt when sending to the ml as well, so i went out looking for their list guidelines, something i should probably have read years ago15:43
gagehugooh ok15:43
gagehugo"confirm that you indeed read this policy before successfully sending anything to us." haha15:44
fungiexactly ;)15:44
gagehugohmm they give the key to use there15:45
fungiyep15:45
gagehugoyeah should update our process then15:45
fungiit doesn't come up often because we do embargoed disclosures only rarely, but it would still be best to follow their recommendations when notifying them15:46
gagehugoyeah15:46
gagehugoI need to hop on another meeting, thanks fungi!15:47
gagehugo#endmeeting15:47
opendevmeetMeeting ended Thu Nov  4 15:47:53 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
opendevmeetMinutes:        https://meetings.opendev.org/meetings/security/2021/security.2021-11-04-15.01.html15:47
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/security/2021/security.2021-11-04-15.01.txt15:47
opendevmeetLog:            https://meetings.opendev.org/meetings/security/2021/security.2021-11-04-15.01.log.html15:47
fungithanks gagehugo!15:47

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!