Page 1 of 1

I think another Hacker keeps getting me

Posted: Fri Oct 06, 2006 5:19 am
by Theneler
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?

Posted: Fri Oct 06, 2006 1:06 pm
by alphager
a) When you get disavowed, you get the info about which company got you. Perhaps you are cleaning up the wrong company.
b) are you sure you are using a log-deleter which is good? Which level does your log-deleter have?

Posted: Sat Oct 07, 2006 1:14 am
by Theneler
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.

Posted: Sat Oct 07, 2006 1:44 am
by Theneler
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.

Posted: Sat Oct 07, 2006 6:39 pm
by frenchfrog
Perhaps the order to capture your gateway is already sent to the FBI.

Posted: Sun Oct 08, 2006 3:14 pm
by Krid
Perhaps you deleted the log entry for your connection to internic?

Posted: Mon Oct 09, 2006 10:09 pm
by ReconMikel
have you installed security on your gateway? You can detect the Feds poking around then blow up your gateway in the nick of time, you know!

Posted: Tue Jan 23, 2007 10:53 pm
by zienkik
Is it not possible that some hacker was hired to frame you? I would chack the mission board from your oldest save to see if there were any "Trace this hacker" missions that you can't accept.

Posted: Wed Jan 31, 2007 8:13 pm
by mike1350
I think your best bet is to just nuke your gateway.. Put any important files in a File Server and nuke it :P

Posted: Thu Feb 01, 2007 12:27 am
by lunchlady55
I think that what's going on is you're deleting the wrong set of logs on 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.


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?

Posted: Thu Feb 01, 2007 12:47 am
by Montyphy
It doesn't look for suspious logs such as being connected for long periods or missing connect/disconnect logs. It only looks for logs created during the timeframe of the hack.