full-disclosure - Re: one of my servers has been compromized

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 06 Dec 2011 10:17:20 +0100
From: Lucio Crusca <lucio@...web.org>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: one of my servers has been compromized

Gage Bystrom wrote:
> I would suggest iptables but the OP stated he doesn't own the
> server and has no root access. 

If I ever stated that, it means I misused my poor english for sure... I DO 
have root access and I DO own the server, where the server means the *guest* 
OpenVZ instance. I DID configure iptables yesterday in order to block 
outgoing connections. What I can't do is upgrading the kernel because OpenVZ 
is a limited "paravirtualization" system where the guest kernel it's more 
like a stub on top of the only shared host kernel. I have no control over 
the host kernel, so I can't upgrade it.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/