uidnobody

9 ms·

1.
by uidnobody 2y ago
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 furt
2.
by uidnobody 2y ago
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 b
3.
by uidnobody 2y ago
OP's advisory on this posted to github https://github.com/hackerhouse-opensource/exploits/blob/mast...
4.
by uidnobody 2y ago
so fix the issue by chown the pty created by systemd and give the OP his dues for pointing the issue out, seems like unnecessary flaming beyond that as to why this can be used to freely hijack root permissions with ptrace_classic and tty io
5.
by uidnobody 2y ago
in the case of systemd the pty remains user owned once the root program is attached, this allows any user process to read and hijack the root program. sudo, su and doas ymmv. The suggested fix for systemd is to chown the slave pty to the us
6.
by uidnobody 2y ago
3rd example, its a pty permission problem as the OP said in his initial post and he suggested a tested fix. https://x.com/hackerfantastic/status/1786485377617846348
7.
by uidnobody 2y ago
https://x.com/hackerfantastic/status/1786485377617846348 gives a 3rd example to explain the problem and suggests a fix. The pty should be chown() to root after a root program is attached.