[blucaz]

The only thing this demonstrates is that the author has no clue about how these things work on Linux. There is no real security boundary between different processes of the _SAME_ uid, especially when controlling the parent process. The exact same "hijacking" can be done to literally any other tool, including sudo. Or you can take over the X11 session and sniff passwords and whatnot. Or heck you can just append alias sudo='mykeylogger sudo' into bashrc and go to the pub instead of having to wait for the right process to start at the right time. If you have write and execute privilege of a user, anything that user does can be compromised.

The reality is that this is just self-promotion from a grifter, and that's why it's happening on Twitter. If it was a real issue from a competent researcher it would have been reported via the appropriate channels, not on social media to feed haters and trigger the usual abuse and death threats while chasing impressions.

[uidnobody]

the op was sent harassing messages and insults by the package maintainer, who are you to demand how and where people discuss security issues? the write up on github is very detailed and identifies a vulnerability added by systemd that can be fixed. Systemd claiming its a victim of abuse and death threats is laughable when they instigated attacks on the OP and his credibility. Calling security researchers grifters for sharing their work is ultimately harmful to users.

[blucaz]

No, the OP was not sent any harassment, the OP _did_ the harassment as it can be seen in the tweets. I mean, they are right there, just click on the links you shared. One of the OP's followers even openly called for the assassination of the project maintainer, and you have the galls to defend him? This is truly deranged stuff.

And again, there is no "vulnerability", there is simply a person that doesn't know how Linux works and has learned something new. Which again it's fine, nobody knows everything and we all learn new things everyday, it's just that normal and sensible people don't use that to make grand claims on social media and start harassment campaigns culminating in death threats.

Professional security researchers responsibly report real issues using the appropriate channels, such as defined at: https://github.com/systemd/systemd/security/policy this is not the work of a researcher, this is a grifter looking for self-promotion on social media.

[uidnobody]

You're just making stuff up here, the OP was sent abuse firstly by pottering and handled the situation quite professionally by providing a detailed overview of the issue he posted and responding to the maintainers deflections with further information. The OP sent no death threats and posted about his perspectives and technical data on what he sees as a medium risk issue in systemd's pty handling. Why not chown the pty as he suggests, reduce the risk and thank him for giving his time freely on this matter? Conflating the behavior of others against Pottering as somehow someone discussing systemd publicly being responsible is classic DARVO actions. The OP was attacked by pottering, not the other way around.

[Foxboron]

Matthew was shitting on systemd and pulling no shots. Poettering calling Matthew a scriptkiddie is mild.

He did call me a "facist weenie" with no clear reason why beyond me pushing back on their grand claims.