News for hackers. Stuff that matters.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation by elorm on Tuesday September 10, 2024 @03:59AM (#41498317)
Can't tell what happened to the earlier link but I've fixed the it.

Puck was being malicious in releasing the information. There's no favourable way of describing disclosing a vulnerability on social media because the maintainers didn't meet your 7 day deadline.

It's more of "we're forcing their hands since they haven't met our expectations yet" thing.

There's so many ways they could've gotten a timely fix without "doing everyone a favour by not fully disclosing the entire 0 day." approach but like you said .... tough cookies all round.

Re:Nix 2.24 is vulnerable to (remote) privilege escalation by NotEvil on Tuesday September 10, 2024 @05:59AM (#41499139)
That's not a patch. It's just downgrades the nix version to 23 in nixpkgs.

It doesn't help people who are already using the vulnerable version and also new users cuz installers install latest versions

Re:Nix 2.24 is vulnerable to (remote) privilege escalation by grayhatter on Tuesday September 10, 2024 @09:57AM (#41500816)
> Puck was being malicious in releasing the information.

[citation needed]

> There's no favourable way of describing disclosing a vulnerability on social media because the maintainers didn't meet your 7 day deadline.

personally I'm grateful he didn't sit on a remote privexc vulnerability for 90days when he was confident it wasn't going to be fixed. I think you're conflating public disclosure (security though obscurity) with real harm, compromise due to the bug. If Puck found it, others who would gladly sell it for coin on the black market, would have found it.

Re:Nix 2.24 is vulnerable to (remote) privilege escalation by 3np on Tuesday September 10, 2024 @02:52PM (#41504211)
Calling the reporter malicious is not constructive and does not help Nix (even if you are right). From all I can tell, there was no request to extend the deadline or proactively coordinating disclosure when the reporter pushed for it. That would have been preferred and could have avoided this situation. I would hope for a later postmortem incorporating the lesson of more proactive communication with reporters.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation by soraminazuki on Tuesday September 10, 2024 @10:13PM (#41507482)
That the Nix team didn’t cooperate is a trivially disprovable excuse being pushed by people surrounding the fork.

https://matrix.to/#/!VRULIdgoKmKPzJZzjj:nixos.org/$tJgEBGqKs...

Re:Nix 2.24 is vulnerable to (remote) privilege escalation by 3np on Wednesday September 11, 2024 @04:16AM (#41509225)
[delayed]
Re:Nix 2.24 is vulnerable to (remote) privilege escalation by soraminazuki on Wednesday September 11, 2024 @06:05AM (#41509834)
The thing is, the reporter is not a random independent security researcher. She's a core team member of Lix, the fork, and is no stranger to the Nix community. This incident directly relates to the wider conflict between the two projects. That's why people are upset.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation by johnklos on Wednesday September 11, 2024 @05:58PM (#41515687)
So you're saying out loud that the person reporting the issue matters. It shouldn't matter who tells you that you have a security issue.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation by soraminazuki on Wednesday September 11, 2024 @10:18PM (#41516980)
Nobody ever said it isn't okay to report security issues. This is about dumping 0 days on social media when you know fully well that the other side is cooperating and working on a fix. The who in this case matters because the reporter knew how the Nix community works, knew it was hostile thing to do, and did it anyways.

Again,

https://matrix.to/#/!VRULIdgoKmKPzJZzjj:nixos.org/$tJgEBGqKs...

What I meant is crystal clear if you read what I was replying to. Please don't take it out of context to spin a story. You did it in your original comment, and you did it again right here.

Re:Nix 2.24 is vulnerable to (remote) privilege escalation by johnklos on Friday September 13, 2024 @03:38PM (#41534430)
No, I'm really not trying to take things out of context, but what you wrote really makes it seem like the person who reports it matters.

Ignoring that, I agree that it's a dick move, but it's like our famous "well, technically" memes - the delivery might matter, but in the case of security issues, it really doesn't matter as much as the actual content.

"You have an issue, and I'm going to be a dick and release it in a week."

Yes, that would be a dick move, but someone acting like a dick doesn't mean that the Nix team shouldn't address the issue within that week, even if it does feel like extortion.

Also, those matrix links say nothing. I'm not sure what we're supposed to do with them, but I'm not downloading software to see whatever it is you want to share.