Wednesday, 2026-11-04

opendevreviewMerged openstack/governance master: Mark SRBAC goal completed  https://review.opendev.org/c/openstack/governance/+/100991200:23
mikalgouthamr: noting that the broad capabilities was a deliberate design decision taken at the time by Nova. It was not the originally proposed implementation. I assume that has been discussed and I just didn't notice?18:33
gouthamrmikal: i am unsure if that was discussed (or evolved over time).. the team was at some point looking at modifying nova to use multiple privsep contexts: https://blueprints.launchpad.net/nova/+spec/privsep-usage-review18:40
gouthamrwork's stalled afaics.. 18:40
gouthamrhttps://review.opendev.org/c/openstack/nova/+/87172918:40
mikalgouthamr: the initial proposal was more granular, but was walked back at a PTG because of concerns about the stability of the set of capabilities required for given calls in the kernel. IIRC it wasn't a documented / stable interface at the time. Honestly, if not everyone has transitioned at all surely getting that done is more important than tuning18:52
mikalthe exact capabilities in projects which have adopted it?18:52
gouthamrI agree; we’ll get the stragglers addressed  this release18:54
gouthamrill nudge Oslo folks signal oslo.rootwrap’s deprecation - it’s informally spoken about so far 18:55
sean-k-mooneygouthamr: yes at some pont btu that kind of stalled out20:15
sean-k-mooneybut we are also usign some legacy capabity defeingion that are semi deprecated in the kernel too20:15
sean-k-mooneyi tried to remove CAP_DAC_OVERRIDE in the past, nova only uses it for one lvm interaction at elast wehn i last tried to remove it an di had a plan to do that but never got time to finish it20:17
sean-k-mooneyhttps://www.man7.org/linux/man-pages/man7/capabilities.7.html20:17
sean-k-mooneyalsome all project that have adopted it have some combination of CAP_DAC_OVERRIDE CAP_SYS_ADMIN and CAP_NET_ADMIN20:18
sean-k-mooneywich is almost but not quite full root20:19
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/privsep/__init__.py#L2120:21
sean-k-mooneyhttps://github.com/openstack/neutron/blob/7157cab2caf48d0b3a7fe0ab9f0f09fa7e109c2c/neutron/privileged/__init__.py#L18-L7320:21
sean-k-mooneyneutro is slightly better.20:21
sean-k-mooneybut cidner also has the same permisions as nova https://github.com/openstack/cinder/blob/master/cinder/privsep/__init__.py20:22
sean-k-mooneyi will try and eventually audit cybrogs usage and see if we can drop https://github.com/openstack/cyborg/blob/8f58f18b90de98a047dabc93a7c5f41b0a4ae656/cyborg/privsep/__init__.py#L20-L3420:24
sean-k-mooneybut ya movign to privesep by itself is not more secure the is not nessiarly any more secure then just using raw sudo without a lot of work on the project to carfully limit scope20:26
sean-k-mooneythe problem is that each privsep context has its own deamon and need to load the prouces code into memroy in a new python interpertry to service it request20:26
sean-k-mooneyso its a memory vs secuirty vs performace trade20:27
opendevreviewMerged openstack/openstack-manuals master: Fix www/project-data/latest.yaml  https://review.opendev.org/c/openstack/openstack-manuals/+/101132820:48
opendevreviewMerged openstack/openstack-manuals master: Update 2026.2 docs page links  https://review.opendev.org/c/openstack/openstack-manuals/+/101132920:49
opendevreviewMerged openstack/openstack-manuals master: [www] Set 2025.1 Epoxy state to Unmaintained  https://review.opendev.org/c/openstack/openstack-manuals/+/101391621:12
gouthamrsean-k-mooney: yeah, well put.. i think there's a bunch of compromises/design decisions that project teams took considering that trade-off (or sometimes not)... a couple of thoughts around this, i would love to have some guidelines in the docs themselves for developers - and maybe the per-project threat model that we sought will surface what the project decisions looked like, and any pending tasks they imagined.. 21:23
gouthamrright  now, the old spec https://specs.openstack.org/openstack/oslo-specs/specs/liberty/privsep.html is more comprehensive than the official docs21:24
fungiJayF: worth noting, enisa is making references to "security.txt" files in https://www.enisa.europa.eu/sites/default/files/2026-10/Technical%20Advisory%20on%20security.txt%20CVD%20Policies%20and%20Security%20Advisories%20Public%20Consultation.pdf which might be worth pointing out to your github contact too21:56
JayFack, ty21:57
fungithough it's more in context of web sites/applications e.g. https://yourdomain.example/.well-known/security.txt rather than in git repositories specifically22:00
gouthamrseems like they are standardizing on https://www.cisa.gov/news-events/news/securitytxt-simple-file-big-value ?22:00
gouthamrhttps://www.rfc-editor.org/info/rfc9116/22:00
fungigouthamr: yes, it makes references to ietf rfc 9116 for that22:02
fungii don't think enisa is going to directly recommend a cisa directive, that's from a completely different (and potentially antagonistic) jurisdiction22:03
gouthamryeah :P i was just curious22:03

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