[ubuntu] Worried about rootkit hunter results topic

Hi, my VPS was recently compromised and infected. The hosting company told me that they've cleaned the server of the infection, however I've ran a rootkit hunter scan and seen a few worrying things. Here is the full scan, the things I'm not sure about are highlighted in bold..

Code:

---

root@badbox:~# sudo rkhunter -c --enable all --disable none --rwo
Warning: The following processes are using deleted files:
        Process: /usr/bin/tgfvvtxvse    PID: 1608    File: /usr/bin/tgfvvtxvse
        Process: /usr/bin/tgfvvtxvse    PID: 1611    File: /usr/bin/tgfvvtxvse
        Process: /usr/bin/tgfvvtxvse    PID: 1612    File: /usr/bin/tgfvvtxvse
        Process: /usr/bin/tgfvvtxvse    PID: 1615    File: /usr/bin/tgfvvtxvse
        Process: /usr/bin/tgfvvtxvse    PID: 1621    File: /usr/bin/tgfvvtxvse
        Process: /usr/bin/sudo    PID: 3809    File: /dev/pts/0
        Process: /bin/dash    PID: 3810    File: /dev/pts/0
        Process: /usr/bin/xinit    PID: 4044    File: /dev/pts/0
        Process: /usr/bin/xfce4-session    PID: 4061    File: /dev/pts/0
        Process: /usr/bin/dbus-launch    PID: 4092    File: /dev/pts/0
Warning: File '/tmp/gvxddrshkl' (score: 206) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-1068.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-26937.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-4536.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-1073.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-27797.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-4291.log' (score: 221) contains some suspicious content and should be checked.
Warning: File '/tmp/vmware-root/vmware-apploader-28589.log' (score: 221) contains some suspicious content and should be checked.
Warning: Checking for files with suspicious contents [ Warning ]

---

Does anybody have any idea about what these randomly named files/processes I highlighted could be? Right click -> properties says it's an executable. I can try to upload the contents of the file onto pastebin however I'm not sure if that is against the forum rules or not - so if it's allowed and needed then ask.

I really don't know much about this kind of thing so if there is any information I was meant to provide please ask for it and I'll do my best to provide it.

Best regards

..Also, how can I whitelist .log files?

[ubuntu] AMD R9 290X test results on Vivid topic

I got the AMD R9 290X courtesy of Canonical on Thursday. Been puttering around from Precise through Vivid.

Um. I'd really love to give a detailed report on all sorts of things wrong. But I can't. It works great with the driver available in the repo. But I really can't comment on gaming performance, since I don't do that much. TF2 looked pretty great until I got killed about 30 seconds in like always. But the Phoronix Test Suite GLMark2 test, with all the settings in CCC maxed out and Tear Free enabled, held a steady 60 FPS. Not bad for all the quality setting set to full-on. So I imagine that will make the gamers happy if they tune it a bit for performance.

With the open source driver, not so much. Performance was terrible.

The one thing I initially thought might be a problem -- a single line of white pixels at the bottom of one of the monitors when Tear Free was enabled -- turned out to be just a matter of "jiggling" the positions of the three monitors in Catalyst to get them aligned perfectly.

One thing to watch out for, as has been going on for me off and on for several releases, is that you don't want to shut down/reboot with Tear Free enabled if you are running multiple monitors. When it starts up again, a couple of them may not be detected. To solve that, you have to drop in to root at boot, mount rw, uninstall the driver and reboot with the open source driver.

More details in a nice write-up later for public consumption. The gist of that will be: For currently supported releases (except for < 12.04.2) the R9 290X runs great. If you buy this thing, go ahead and upgrade if you have 12.04 or 12.04.1.