Live data from Hacker News

Hack Back – A DIY guide to those without the patience to wait for whistleblowers

data.langly.fr

61–62 of 62 posts

Re: Hack Back – A DIY guide to those without the patience to wait for whistleblowers

#61

If you are as curious as I am and decide to browse langly.fr for other interesting stuff: Don't click on links that say "...dont clik" and if you absolutely must, turn down the volume or put down your headphones and be prepared to restart your browser.

Or just don't have flash installed.

Re: Hack Back – A DIY guide to those without the patience to wait for whistleblowers

#62
post #45

Earlier quoted context omitted.

Because they never gained root access. I trust the logs in this case because their actions were immediately made known: Access logs show failed login attempts from that ip for a range of usernames, a successful login on the compromised account, then nothing but reams of mail being churned out. If it had been done for more nefarious purposes, wouldn't "they" have been more discreet, carefully wiping traces of their ac…

> I can erase or alter logs, but then there are logs logged of me vi'ing logs, so I erase the shell history, but then that gets logged when I log out. It's a weird loop I don't know how to defeat, but some people do. This is trivial, but you need to be familiar with the environment variables used by bash. unset HISTFILE

Or kill the shell from within, avoiding history write:

    $ vi /var/log/*.log
    $ kill -9 $BASHPID
Post reply on HN