this is truly incredible: https://github.com/X11Libre/xserver/pull/1627/files

[ariadne@social.treehouse.systems]

this is truly incredible: https://github.com/X11Libre/xserver/pull/1627/files

they are using system(3) inside a security-critical domain (the display server).

but yes, sure, my refusal of xlibre on security grounds is the problem

[dio9sys@haunted.computer]

@ariadne
breaking news: the x11 fork for chuds learning in realtime why it's useful to keep gay furries on your security team

[tauon@possum.city]

@ariadne@treehouse.systems oh my fucking god why are they doing it like that

[erikarn@mstdn.social]

@Dio9sys @ariadne (cry can't we have a managed x11 fork that keeps the gay furries involved? pretty please? Ill create it if we need it)

[e_nomem@hachyderm.io]

@ariadne Wait, so I just need to sneak in a binary named zenity to the front of the PATH to get it executed in an elevated security context?

[oblomov@sociale.network]

@ariadne wow there's so many issues with that commit I don't even know where to start.

[ariadne@social.treehouse.systems]

there are quite a few reactionaries in my comments, some of which have been defederated in their entirety.

for the others:

1. although the system("which ...") use is silly, that isn't the problem here.

2. what do you think will happen when the code in this PR encounters a process named `" && :() { : | : & }; :&`? will it safely handle such a process name? before saying "that's impossible" please read setprocname(3), setproctitle(3), or in the case of Linux, understand that argv[0] is mutable.

3. yes, it is an open PR. it is also reflective of the code quality of many other PRs which have been merged to Xlibre already. how do you think that impacts its security record?

[ariadne@social.treehouse.systems]

and yes, sometimes i post these things as bait to find out if we are missing alt-right reactionary servers that we need to defederate. it's like vaccines but for social media ❤️

[ariadne@social.treehouse.systems]

vaccines are good btw

[ariadne@social.treehouse.systems]

by the way, the ":() { : | : & }; :&" part earlier? that's a forkbomb. don't run it unless you want to deal with the consequences of running a forkbomb (in most cases, hard rebooting).

[gunstick@mastodon.opencloud.lu]

@ariadne or replace the hardware. A student ran a forkbomb. The PC got hot and ran for a weekend with all fans at max. Week after: fan error. The fan controller, hard soldered to the main board, was faulty.