|
|||||||||||
|
Re: ping22: can not kill this process
From: Luis Mondesi <lemsx1(at)gmail.com>
Date: Tue Jan 01 2008 - 20:21:19 EST
Happy new year to all as well! > I checked cron/at job, nothing related to ping22. Did you check to see whether /usr/sbin/apache2 was modified? Or was it only the running process that had somehow been stack-overflow'd? IMHO, I'd declare this box as "compromised" and redo the whole thing. Copy all data to a new box and install tripwire (or something of that sort), plus follow the Debian security manual to the last bit, before putting the box online again. A few links: http://www.debian.org/doc/manuals/securing-debian-howtohttp://wiki.debian.org/SELinux/Setuphttp://wiki.debian.org/Hardening|Hardening I know that you already had SELinux enabled (after the fact?). So, you might already have enough information to build a better box. -- ----)(----- Luis Mondesi Maestro Debiano ----- START ENCRYPTED BLOCK (Triple-ROT13) ------ Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. ----- END ENCRYPTED BLOCK (Triple-ROT13) ------ -- To UNSUBSCRIBE, email to debian-security-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Tue Jan 1 20:22:17 2008 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 06:54:51 EDT |
||||||||||
|
|||||||||||