Unless you can identify a benign cause for this in short order, you've probably had your server cracked. I would highly recommend taking it offline ASAP and imaging its disks for forensic purposes. ![]() ![]() This video will help you to fix the below-mentioned errors. If it's more of a personal machine, might there be a knowledgeable prankster who's had access to it recently?Įdit: your comment to another answer suggests that this is a server. When you use Linux, you can get the below-mentioned error, while you try to edit a file -/etc/apt. In that case, you should probably back up the data, do a clean re-install, and audit anything that goes back on it. Is this machine offering any network services? If so, someone may have broken into it and taken it over. The bigger issue here is how such a condition came to pass. You should also post the output of getent passwd root Once you know the name, you can try sudo -s -u username Whatever account that is is the real superuser on the system, while root is a fake. When you ran sudo -s, you were given a UID of 1, while the only UID that the kernel will recognize as having root privileges is UID 0.Īnd see if any entries have that 0 in their first numeric field, the UID. The output of id here is quite enlightening. ![]() And post the output? I want to see if it's actually making you the user you think.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |