Cannot delete log files (first mission)

[Professor Von-Wulfen ]

Hi all.
I am at the end of a successful first mission but Unable to finish as I cant work out how to delete the shell entries in the log.
Any advice most welcome.
Cheers
https://steamcommunity.com/sharedfiles/filedetails/?id=2543428299

[Professor Von-Wulfen ]

Found this video that really helped :)
https://www.youtube.com/watch?v=qtfaag14Qf4

[HEX0940593]

tip:
the only logs you need to delete is

shell obtained
file deleted

deleting any other log will make the admin suspicious.

[Japple12321]

you can run viewlogs.exe in root and delete them

[b0nehead]

You can delete the whole log period, dont even waste your time. The log is recreated only after you dc.

[Professor Von-Wulfen ]

A lot to learn but its fun :)

[Xephael]

Originally posted by Wanted514:

You can delete the whole log period, dont even waste your time. The log is recreated only after you dc.

If you do that the admin will often trace you.

[Professor Von-Wulfen ]

Originally posted by Xephael:

Originally posted by Wanted514:

You can delete the whole log period, dont even waste your time. The log is recreated only after you dc.

If you do that the admin will often trace you.

I only deleted the shell log :)

[b0nehead]

Originally posted by Xephael:

Originally posted by Wanted514:

You can delete the whole log period, dont even waste your time. The log is recreated only after you dc.

If you do that the admin will often trace you.

You should be long done before that active trace comes. And the passive one, there is nothing to start with since you rm the log. You can even wipe the chain as you "exit" out of accounts. Within seconds.

But yes removing shell/redirects is not difficult and if you need more time then you don't want to piss the admin off.

[Xephael]

Originally posted by Wanted514:

Originally posted by Xephael:

If you do that the admin will often trace you.

You should be long done before that active trace comes. And the passive one, there is nothing to start with since you rm the log. You can even wipe the chain as you "exit" out of accounts. Within seconds.

But yes removing shell/redirects is not difficult and if you need more time then you don't want to piss the admin off.

When you delete the log it is instantly recreated with a deletion entry, which on its own is enough to get you traced. It also gets a connection closed log when you leave which will get you traced if there is no connection established log.

[b0nehead]

Originally posted by Xephael:

Originally posted by Wanted514:

You should be long done before that active trace comes. And the passive one, there is nothing to start with since you rm the log. You can even wipe the chain as you "exit" out of accounts. Within seconds.

But yes removing shell/redirects is not difficult and if you need more time then you don't want to piss the admin off.

When you delete the log it is instantly recreated with a deletion entry, which on its own is enough to get you traced. It also gets a connection closed log when you leave which will get you traced if there is no connection established log.

Well to be fair i only rm these logs on an older version. I had noticed that when you reconnect to server there was no disconnect in logs from the last session.

Maybe in the current version which i havent tried the dirty method its not possible.

Bad advice to give then !

[Xephael]

Originally posted by Wanted514:

Originally posted by Xephael:

When you delete the log it is instantly recreated with a deletion entry, which on its own is enough to get you traced. It also gets a connection closed log when you leave which will get you traced if there is no connection established log.

Well to be fair i only rm these logs on an older version. I had noticed that when you reconnect to server there was no disconnect in logs from the last session.

Maybe in the current version which i havent tried the dirty method its not possible.

Bad advice to give then !

That's a log bug that was happening occasionally, I'm not sure if it's been fixed, but it's not consistent so I wouldn't rely on it.

[b0nehead]

Originally posted by Xephael:

Originally posted by Wanted514:

Well to be fair i only rm these logs on an older version. I had noticed that when you reconnect to server there was no disconnect in logs from the last session.

Maybe in the current version which i havent tried the dirty method its not possible.

Bad advice to give then !

That's a log bug that was happening occasionally, I'm not sure if it's been fixed, but it's not consistent so I wouldn't rely on it.

Wow so i had a bug the one time i tried to verify lol. What a horrible assumption i led on.

For me though it didn't feel legit so i always did it manually (delete shell+redirects). I suggested it here simply if someone did not care about that. But it's wrong.

[DㅌFㄷㅁN]

To delete the log entry, you must first authenticate as root. To do this, you need to use Decipher to obtain the root password, which is located in /etc/passwd. Once you have the root password, on the machine where you want to delete the log entry, use the command "sudo -s". It will ask for the root password (the one you just cracked), and from there, you can go to LogViewer, which will allow you to delete the generated log entries.

[solipse49]

dont delete it touch it.