> "The hackers left no trace" What does it mean

>>59031103
>"I have no idea what happened here... but I cannot say that to the media."

>>59031103
There's also ~/.bashrc

>>59031136

ok, rm .bash_history && exit -- done ?

>>59031136
And SELinux will also log by itself.

>>59031144

I have full root and disable SELinux

no 'follow the white rabbit' left in the logs senpai

>>59031154

sudo rm /* && sudo reboot

>>59031103
By hacking with compiled binaries instead of skiddy bash commands

>>59031180
teach me senpai

you need to replace the binaries with your own ones first.

It means the one who got hacked didn't have a proper system for logging.

>>59031196
Once you get access you replace the GNU usertools with yours that don't leave traces.

>>59031103
It means somebody accidentally the production server and blamed it on hackers to keep his job.

>>59031118

your site is fucking shit.

>>59031154
>I have full root and disable SELinux
Not possible in a properly secured environment.

>>59031268
lol

>>59031103
I'm not sure, but I believe it's a part of Linux?

>>59031103

a) "We didn't care about computer security until now. Mgmt said we don't need this 'intrusion detection system' thingy.."

b) "We realized it after two weeks and there was nothing the IT forensic guy could do anymore since everything as overwritten already."

c) "We f*cked up something really bad and blame russian hackers for it."

d) "We have no clue what's going on. Maybe it was just an angry employee? We will porbably never knnow."

>>59031103
it means the hackers used freedos

>>59031103

It means there were no hackers at all, only a pfy trying desperately to offload resposibility for fucking up

What about using an app like Bleachbit?

incognito mode and hidemyass, easy undetected invasion

>>59032330
>mawm i can hak tha guverment!
>ping 127.0.0.1
>SEE?

>>59031118
/bread

also filtered

>>59031103
First of, they used some kind of IP spoof technique.

>>59031268
You did that, didn't you, anon? You can tell us.