Comment 36 for bug 454566

Revision history for this message
Madden (mrsexy) wrote :

Alright did some checking for myself, I just went ahead and did the sha256sum checks on my own as well as hardlink check.

I've made a tutorial to check yourself
--------------------------
Testing with Sha256sum/md5sum
First we want to make a sha256sum or md5sum of the init in our system. To do this open terminal and...
# cd /sbin
# sha256sum init
You will get a long code, paste it into a text editor.
Next..
if you are using "trusty"
Go here: http://packages.ubuntu.com/trusty/upstart
if not go here
http://packages.ubuntu.com/search?keywords=upstart&searchon=names&suite=all&section=all
under "package upstart" find yours

Once on the package page...(Upstart)
go down to the bottom and click the download link for your architecture
once downloaded, right click on the .deb file and click extract here.

Now in the newly extracted folder we downloaded open it then open sbin folder, then in terminal type "sha256sum " and drag n drop init file there into terminal.

You will get yet another long code.

Go back into the text editor and paste that code below your previous one.
Do they match? Good! They don't? Make sure you downloaded the correct upstart. If you still do the hardlink below and it fails, then maybe a reinstall is needed.

Testing with hardlink
In terminal type
# cd /sbin
# ls -l init
Does it show 1? Good.
Now do this..
# ln /sbin/init /sbin/init2
# ls -l init
Does it STILL show 1?
It's infected if it still shows 1..
Do this afterwards to remove the file we just made(cleanup)
# rm init2
--------------
Good luck!