21–30 of 155 posts
Repositories controlled by accounts based in mainland China and Russia are always a risk- it's too easy for a dictatorship to force something to happen even if the authors themselves are trying to act in good faith.
XZ, Swoole... examples off the top of my head.
Earlier quoted context omitted.
No clue personally, but the author is prolific enough here that I thought it merited posting.
I go with three paths out. 1. it consumes too much systems resources. So its net-negative impact on the system under observation 2. it's misleading and leads to false diagnoses of situations under review 3. she's under an NDA of some kind related to a CVE or some other high class risk which will come out in due course but she felt a burden to stop people being exposed to risk. 4. I can't count and there are 4, 5, 6 o…
It has to be 3.
And she knows her stuff, so I'm listening. Luckily we don't use atop.
I stopped using atop when I found it installs several hooks which automatically run code as root and deposit files around the filesystem, including a "power management" hook.
There's a lot of speculation about why, with the answer almost certainly security / exploitable (or backdoor), and I'll just throw an extra little tidbit in: atop seems to run persistently as root, which may be the reason for preventing it from running/uninstalling. the netatop part of atop installs a persistent kernel module, netatop.ko, as part of its installation. The module hooks netfilter to be able to monitor a…
Earlier quoted context omitted.
No clue personally, but the author is prolific enough here that I thought it merited posting.
I go with three paths out. 1. it consumes too much systems resources. So its net-negative impact on the system under observation 2. it's misleading and leads to false diagnoses of situations under review 3. she's under an NDA of some kind related to a CVE or some other high class risk which will come out in due course but she felt a burden to stop people being exposed to risk. 4. I can't count and there are 4, 5, 6 o…
There's a lot of speculation about why, with the answer almost certainly security / exploitable (or backdoor), and I'll just throw an extra little tidbit in: atop seems to run persistently as root, which may be the reason for preventing it from running/uninstalling. the netatop part of atop installs a persistent kernel module, netatop.ko, as part of its installation. The module hooks netfilter to be able to monitor a…
I'm not familiar with atop but the website mentions netatop is optional and what I've found suggests you have to manually install it. Do you know if any distributions/packages install this by default alongside the atop install?
Earlier quoted context omitted.
I'm not familiar with atop but the website mentions netatop is optional and what I've found suggests you have to manually install it. Do you know if any distributions/packages install this by default alongside the atop install?
This is a good question - I'm not sure. The rpmspec doesn't seem to install it, so perhaps it's not quite that bad. The atop program _itself_ runs persistently, though, so, uh, still bad. :)
I’m actually surprised I didn’t have it installed, what with all the packages I check out just through sheer curiosity. Thanks Rachel! I’ll avoid it in the future.
This screams NDA/disclosure but things are so mega super fucked that they feel obligated to pre warn as early as possible. I wonder how long/old the problem is in atop?
She likely can't disclose anything right now.