# Cover your tracks

<http://www.dankalia.com/tutor/01005/0100501003.htm>

### On Linux <a href="#on-linux" id="on-linux"></a>

#### Log files <a href="#log-files" id="log-files"></a>

`/etc/syslog.conf`

In this file you can read all the logs that syslog log.

On linux systems a lot of logs are stored in:

```
/var/logs
```

For example:

```
/var/log/messages
```

Here you have failed and successful login attempts. SSH, SUDO, and much more.

```
/var/log/auth.log
```

#### Apache <a href="#apache" id="apache"></a>

```
/var/log/apache2/access.log
/var/log/apache2/error.log
```

Remove your own ip like this

```
grep -v '<src-ip-address>' /path/to/access_log > a && mv a /path/to/access_log
```

What it does is simply to copy all lines except the lines that contain your IP-address. And then move them, and them move them back again.

```
grep -v <entry-to-remove> <logfile> > /tmp/a ; mv /tmp/a <logfile> ; rm -f /tmp/a
```

#### UTMP and WTMP <a href="#utmp-and-wtmp" id="utmp-and-wtmp"></a>

These logs are not stored in plaintext but instead as binaries. Which makes it a bit harder to clear.

```
who
```

```
last
```

```
lastlog
```

#### Command history <a href="#command-history" id="command-history"></a>

All your commands are also stored.

```
echo $HISTFILE
echo $HISTSIZE
```

You can set your file-size like this to zero, to avoid storing commands.

```
export HISTSIZE=0
```

If you set it when you get shell you won't have to worry about cleaning up the history.

### Shred files <a href="#shred-files" id="shred-files"></a>

Shredding files lets you remove files in a more secure way.

```
shred -zu filename
```

### On windows <a href="#on-windows" id="on-windows"></a>

Clear env <https://www.offensive-security.com/metasploit-unleashed/event-log-management/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cybermuhdupa.gitbook.io/total-oscp-guide/vulnerability-analysis/post-exploitation/cover-your-tracks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.