!ZRgXNaHrdpGqwUnGnj:nixos.org

NixOS Security Triage

703 Members
Coordination and triage of security issues in nixpkgs217 Servers

Load older messages


SenderMessageTime
25 May 2021
@sumner:sumnerevans.comsumner hexa: mentioned that he tested on 20.09 (https://github.com/NixOS/nixpkgs/pull/124276#pullrequestreview-667050318), but I'm not sure the best approach for testing in general since I'm running unstable on all my machines. 03:02:48
@sumner:sumnerevans.comsumner * hexa mentioned that he tested on 20.09 (https://github.com/NixOS/nixpkgs/pull/124276#pullrequestreview-667050318), but I'm not sure the best approach for testing in general since I'm running unstable on all my machines. 03:04:08
@toonn:matrix.orgtoonn Fyi a backport GHAction was recently added might be a good test? 09:38:44
@synthetica:matrix.orgSynthetica"recently"09:38:59
@synthetica:matrix.orgSyntheticaLiterally less than a minute ago :D09:39:05
@toonn:matrix.orgtoonn I'm like a pigeon, time moves very slowly to me : ) 09:39:53
@synthetica:matrix.orgSynthetica But yeah, sumner, you should be able to add the label backport release-21.05 and on merge a PR will automatically be opened now 09:41:04
@hexa:lossy.networkhexaWe are past creating the backport PRs though, which is all the backport action will create.14:04:45
@hexa:lossy.networkhexaAt some point you have to have confidence, that a backport will not break14:05:00
@hexa:lossy.networkhexa merged the 20.09 change, which I already tested, but noticed too late, that the cherry-picked from note was missing 14:07:42
@hexa:lossy.networkhexarequested a change for 21.0514:07:49
@hexa:lossy.networkhexa sumner: ^ 14:07:59
@hexa:lossy.networkhexaReminmder: curl 7.77.0 scheduled for tmorrow https://twitter.com/bagder/status/139657771621694668815:05:34
@hexa:lossy.networkhexa * Reminmder: curl 7.77.0 scheduled for tomorrow https://twitter.com/bagder/status/139657771621694668815:05:40
@hexa:lossy.networkhexa * Reminder: curl 7.77.0 scheduled for tomorrow https://twitter.com/bagder/status/139657771621694668815:06:10
@sumner:sumnerevans.comsumner hexa: maybe it's worth trying the GH action for the backport to 21.05? 15:18:31
@hexa:lossy.networkhexa sumner: it does not work yet, see https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$QslwsZCEf9aeS9DOzAfzUlgkKh4ecPRi-MX2PuwQVzE?via=nixos.org&via=matrix.org&via=fairydust.space 15:19:04
@sumner:sumnerevans.comsumner OK, I updated the backport commit, and rebased on the latest release-21.05 branch for good measure. 15:23:39
@hexa:lossy.networkhexawill merge when ofborg eval is happy15:24:20
@packetizeme:matrix.orgbinaryoctopus joined the room.15:42:22
@meetmangukiya:matrix.orgmeet joined the room.16:06:36
@georgyo:nycr.chatgeorgyo joined the room.16:54:06
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/12440018:31:19
@hexa:lossy.networkhexaneeds porting to both stable branches18:31:30
@hexa:lossy.networkhexa
A security issue in nginx resolver was identified, which might allow an
attacker to cause 1-byte memory overwrite by using a specially crafted
DNS response, resulting in worker process crash or, potentially, in
arbitrary code execution (CVE-2021-23017).
18:31:53
@hexa:lossy.networkhexahttps://security.googleblog.com/2021/05/introducing-half-double-new-hammering.html 😒18:39:03
@kevincox:matrix.orgkevincoxYou mean DRAM manufacturers didn't really fix the problem? surprised-pikachu18:48:07
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/12443322:20:58
@hexa:lossy.networkhexaplease review22:21:07
@hexa:lossy.networkhexathanks for the quick response everbody 🥳22:40:09

Show newer messages


Back to Room ListRoom Version: 6