These are the things that I can think of:
* Last time, I used log deleter v1 for a while until I was able to afford v4, and then started using v4. When I did, I didn't re-delete the old deleted logs. may that have been a problem?
* I usually wonder if that many connections to internic from the same terminal don't look "suspicious" to "sysadmins" in the later phases of the game. Should I change my bouncing route every so often?
* I work with a very long bounce route, first step internic. I hack, I disconnect, I load the bounce route again, cut off internic and then log in to delete the bounce log. This usually means that internic has a lot of connect/disconnect logs from the same IP that hacked the compromised computer (i.e.: the last one in my bounce route). Maybe this is bad? should I connect to internic directly when I go delete logs?
* sometimes I delete the wrong logs, deleting my connect to internic in order to delete the bounce and login as admin logs. In order to avoid unaccounted for disconnect, I usually delete the previous run's disconnect, so I get the connect/disconnect logs paired up (and I tend to think that's even better, since I have a connected log that lasts through the time when the hack was made). But maybe there's a bug in the game, and just having a missing connect log line is "suspicious" even if I fixed things
to clarify, I start up with this:
- -1) disconnect (this will appear afterward)
- 1) login
- 2) connect
- 3) disconnect
- 5) connect
and instead of deleting just 1) I delete 2) as well, so
- -1) disconnect (this will appear afterward)
- 3) disconnect
- 5) connect
to fix this, I do this:
- -1) disconnect (this will appear afterward)
- 5) connect
any clues?
Thanks