!ZRgXNaHrdpGqwUnGnj:nixos.org

NixOS Security Triage

652 Members
Coordination and triage of security issues in nixpkgs | Discussions in #security-discuss:nixos.org | Open PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3A%221.severity%3A+security%22202 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
22 Aug 2025
@june:nekover.seJune joined the room.02:57:43
@julian:nekover.se@julian:nekover.se left the room.03:09:18
@leona:leona.isleonavalkey security release https://github.com/valkey-io/valkey/releases/tag/8.0.515:00:50
@leona:leona.isleonaas far as i see only affects 25.05. https://github.com/NixOS/nixpkgs/pull/43590515:06:30
@elikoga:matrix.orgelikoga changed their profile picture.17:28:13
@odoom:matrix.orgodoom joined the room.21:33:14
24 Aug 2025
@honnip:matrix.orgHonnip joined the room.13:29:06
25 Aug 2025
@lennart:0520.chlennarthej, could someone who is allowed to delete Issues in NixOS/nixpkgs write me directly? I found a vulnerability in a software, made an issue in nixpkgs which partly was about that vuln. upstream asks to please delete the ticket.09:31:16
@lennart:0520.chlennartmy fuckup…09:31:33
@lennart:0520.chlennartalready wrote hexa, I guess he's sleeping or busy :) https://github.com/orgs/NixOS/people/security_managers09:33:22
@lennart:0520.chlennart lassulus did the dead, thanks 09:35:17
@sigmasquadron:matrix.orgSigmaSquadronwe should consider that security vulnerability leaked to the public already, as there may be an archive of the deleted issue.09:49:01
@sigmasquadron:matrix.orgSigmaSquadron * 09:49:15
@tgerbet:matrix.orgtgerbetUpstream should consider the issue public. Information is likely still accessible in GitHub events Full disclosure is better than half disclosed (and apparently the tendency these days is to publish emboarged issues on public ML 🫠 )10:27:45
@lennart:0520.chlennartIt's not related to nixpkgs, only upstream.10:28:01
@lennart:0520.chlennartI see your point, but it'd let upstream cover and decide on that.10:28:27
@lennart:0520.chlennartNonetheless, they'll apply for an CVE number :b10:28:38
@raitobezarius:matrix.orgraitobezariusIf upstream doesn't do full disclosure, this is a very bad look on them for what seems to be a minor issue.10:28:56
@lennart:0520.chlennartWhat do you mean by half and full disclosure? Lets move to the discussion channel?10:29:44
27 Aug 2025
@martijn:boers.emailmartijn joined the room.13:58:51
28 Aug 2025
@hexa:lossy.networkhexa https://github.com/storaged-project/udisks/security/advisories/GHSA-742q-gggc-473g udisks Jan Tojnar 20:55:32
@hexa:lossy.networkhexahttps://www.openwall.com/lists/oss-security/2025/08/28/1 https://www.openwall.com/lists/oss-security/2025/08/28/220:55:56
@hexa:lossy.networkhexa* https://www.openwall.com/lists/oss-security/2025/08/28/120:56:07
29 Aug 2025
@bluebirdlamentations:matrix.org@bluebirdlamentations:matrix.org left the room.16:13:53
@magic_rb:matrix.redalder.org@magic_rb:matrix.redalder.org changed their profile picture.19:27:40
30 Aug 2025
@tgerbet:matrix.orgtgerbet SigmaSquadron: https://xenbits.xen.org/xsa/advisory-471.html
Is this taken into account by the Xen team?
11:13:23
@sigmasquadron:matrix.orgSigmaSquadronuh I already fixed 471 I think11:40:39
@sigmasquadron:matrix.orgSigmaSquadronyeah that's the big one11:41:13
@sigmasquadron:matrix.orgSigmaSquadronwe just updated to the latest branch heads and then updated to 4.20.1 when it released11:41:36
@sigmasquadron:matrix.orgSigmaSquadronditto for 4.19.x on stable11:41:57

Show newer messages


Back to Room ListRoom Version: 6