Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by anonfordays on Tuesday September 10, 2024 @01:45AM
(#41497510)
Yikes. Pierre Bourdon was banned from the Nix community for being toxic. Plugging his software in a thread about nix is bad manners.
[ Parent
| on HN ]
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by akimbostrawman on Tuesday September 10, 2024 @04:10AM
(#41498408)
using "yikes" outside of reddit to concern troll is bad manners.
i appreciate sharing alternative forks that fix problems.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by anonfordays on Tuesday September 10, 2024 @11:15AM
(#41501609)
Tone policing outside of Mastodon to concern troll is bad manners.
I don't appreciate tankies sharing their nonsense after getting kicked out of a community.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by one-punch on Tuesday September 10, 2024 @03:15AM
(#41498040)
I have not been following closely this back story, so I am not aware of such ban, or that (allegedly) Lix is Pierre Bourdon’s software.
I am not affiliated with Nix (Cppnix) or Lix.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by max-privatevoid on Tuesday September 10, 2024 @04:07AM
(#41498387)
Why call it "Cppnix"?
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?
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?
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by pxc on Tuesday September 10, 2024 @10:07AM
(#41500921)
It helps disambiguate Nixlang from the codebase that includes the Nix CLI and the Nix daemon, for one. It's also an unambiguous designation for the original Nix implementation, as opposed to Lix and Tvix.
A Lix user might well reasonably say they 'use Nix' because they use Nixlang. Thus some people are Nix users but not CppNix users. As Tvix matures, the same will be true of Tvix users.
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by bfrog on Wednesday September 11, 2024 @09:13AM
(#41511048)
Because apparently nix isn’t enough despite being the project name, executable name, and the name of the language it implements. No one calls rust “rustrust”
Re:Nix 2.24 is vulnerable to (remote) privilege escalation
by anonfordays on Tuesday September 10, 2024 @03:06PM
(#41504351)
>I have not been following closely this back story, so I am not aware of such ban