I hacked in to the Bionet Mainframe, routing through their Main System.
Shortly after, theres a " Track this hacker " mission that Uplink wont let me access, so i assume its me.
I cleared my logs out of both systems, and internic, but I keep getting disawowed. I have my save game ( don't have patience to keep restarting ) but can't figure it out.
Normally I get sacked april 12, midnight. I went back to the Mainframe, and cleared out more logs and that delayed it 4-5 hours. But I cleared Internic, the Mainframe, and their main system, and I still get caught everytime.
Any suggestions?
I think another Hacker keeps getting me
Moderators: jelco, bert_the_turtle, Chris, Icepick, Rkiver, Punisher Bass
I using V4 the " Impossible to Trace " one.
My profile says I got caught for hacking the BioNet Internal services machine. So I restored, went there, and the logs are empty. Now I routed THROUGH that machine into the mainframe, so I thought, maybe its the mainframe that i left a trace on, but because of the nature of mainframes, it was saying it was the Internal Server. So i went to the mainframe, and i did leave 2 logs there, so I deleted them, then went back to internice and deleted those as well. This delays me getting caught by 4 hours.
My profile says I got caught for hacking the BioNet Internal services machine. So I restored, went there, and the logs are empty. Now I routed THROUGH that machine into the mainframe, so I thought, maybe its the mainframe that i left a trace on, but because of the nature of mainframes, it was saying it was the Internal Server. So i went to the mainframe, and i did leave 2 logs there, so I deleted them, then went back to internice and deleted those as well. This delays me getting caught by 4 hours.
Yeah I definetly can't figure this one out. Just tried again. I get caught for hacking the Biogenic Internal Service machine.
So I went to the mainframe, routed through the Service machine, and deleted all logs. Then i went to the Internal Service machine, deleted all logs, and even destroyed that system using a sys-delete/shutdown. All of this routed through Internic. I then went and deleted ALL logs of internic, except the first login I ever did ( so it showed connect-disconnect ), and i STILL get caught.
So I went to the mainframe, routed through the Service machine, and deleted all logs. Then i went to the Internal Service machine, deleted all logs, and even destroyed that system using a sys-delete/shutdown. All of this routed through Internic. I then went and deleted ALL logs of internic, except the first login I ever did ( so it showed connect-disconnect ), and i STILL get caught.
- frenchfrog
- level5
- Posts: 2572
- Joined: Sun Sep 22, 2002 7:11 pm
- Location: Quebec
-
- level1
- Posts: 37
- Joined: Tue Jan 03, 2006 2:29 am
- Location: The Matrix
- Contact:
-
- level1
- Posts: 19
- Joined: Sat Jan 21, 2006 8:29 pm
I think that what's going on is you're deleting the wrong set of logs on InterNIC:
You wanna delete all your connections prior to the hack and leave one short connect-disconnect, not make it look like you've stayed connected to Internic for 3 straight weeks.
Just after your first hack, you will see this in the Internic Logs:
21:05 password accepted from 127.0.0.1
21:04 connected from 127.0.0.1
21:03 routed 127.0.0.1 to xxx.xxx.xxx.xxx
21:02 disconnected from 127.0.0.1
21:01 password accepted from 127.0.0.1
21:00 connected from 127.0.0.1
Remember that at 21:06 you'll leave a disconnect, so what you'll wanna do is delete it to look like this:
21:04 connected from 127.0.0.1
Now after your second hack, it'll look like this:
21:09 Password Accepted from 127.0.0.1
21:08 connected from 127.0.0.1
21:07 routed 127.0.0.1 to xxx.xxx.xxx.xxx
21:06 disconnected from 127.0.0.1
21:04 connected from 127.0.0.1
Delete everything but the connect at 21:08 and then disconnect. This way it looks like you never even connected to the machine until after the second hack. To a third party hacker all they would see is:
21:10 disconnected from 127.0.0.1
21:08 connected from 127.0.0.1
Vets, please correct me if I'm wrong on this, but if it looks like you've stayed connected to Internic since March 24 won't that throw a red flag?
I then went and deleted ALL logs of internic, except the first login I ever did ( so it showed connect-disconnect ), and i STILL get caught.
You wanna delete all your connections prior to the hack and leave one short connect-disconnect, not make it look like you've stayed connected to Internic for 3 straight weeks.
Just after your first hack, you will see this in the Internic Logs:
21:05 password accepted from 127.0.0.1
21:04 connected from 127.0.0.1
21:03 routed 127.0.0.1 to xxx.xxx.xxx.xxx
21:02 disconnected from 127.0.0.1
21:01 password accepted from 127.0.0.1
21:00 connected from 127.0.0.1
Remember that at 21:06 you'll leave a disconnect, so what you'll wanna do is delete it to look like this:
21:04 connected from 127.0.0.1
Now after your second hack, it'll look like this:
21:09 Password Accepted from 127.0.0.1
21:08 connected from 127.0.0.1
21:07 routed 127.0.0.1 to xxx.xxx.xxx.xxx
21:06 disconnected from 127.0.0.1
21:04 connected from 127.0.0.1
Delete everything but the connect at 21:08 and then disconnect. This way it looks like you never even connected to the machine until after the second hack. To a third party hacker all they would see is:
21:10 disconnected from 127.0.0.1
21:08 connected from 127.0.0.1
Vets, please correct me if I'm wrong on this, but if it looks like you've stayed connected to Internic since March 24 won't that throw a red flag?
Who is online
Users browsing this forum: No registered users and 3 guests