Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by eviks on Tuesday September 10, 2024 @04:37AM
(#41498568)
Because it's written in C++ and the fork plans to rewrite in Rust?
[ Parent
| on HN ]
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by Macha on Tuesday September 10, 2024 @08:26AM
(#41500054)
Also there's too many things called Nix.
There's the overall project, the language, and the primary interpretation. It's also why you'll sometimes see nixlang to refer to the language.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by forgotpwd16 on Tuesday September 10, 2024 @08:50AM
(#41500240)
Thought was the norm using capitalized for language and lower case for the tooling. So Nix/nix, like AWK/awk and Go/go.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by Macha on Tuesday September 10, 2024 @09:05AM
(#41500403)
Full caps AWK feels like a relic from the screaming UNIX days, and golang for Go is incredibly common (and as far as I can tell, the proximate cause of the nixlang term)
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by eviks on Tuesday September 10, 2024 @10:45AM
(#41501315)
Then there is also golang
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by otabdeveloper4 on Tuesday September 10, 2024 @08:55AM
(#41500318)
> fork plans to rewrite in Rust
Lmao. Won't ever happen.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by RaitoBezarius on Tuesday September 10, 2024 @10:40AM
(#41501269)
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by marshycity on Tuesday September 10, 2024 @07:16PM
(#41506614)
oh?