| From: | "Paul J. Adam" <shadowtk@********.demon.co.uk> |
|---|---|
| Subject: | Jen and Gabe |
| Date: | Tue, 2 Jul 1996 23:45:01 +0100 |
>>>>>[Test message. Please ignore.]<<<<<
-- CORRUPTED <CORRUPTED/CORRUPTED>
+++++Stalking Horse v2.5f daemon on trail!
+++++Stalking Horse v2.5f daemon integrity compromised! Now at 57%!
+++++Download diagnostic data? (Y/N)? [Y]
+++++Stalking Horse v2.5f daemon has data!
+++++Download search data (Y/N)? [Y]
+++++Stalking Horse v2.5f daemon still on trail!
+++++Stalking Horse v2.5f daemon failure. Retry (Y/N)? [N]
+++++Stalking Horse v2.5f daemon integrity compromised! Now at 07%!
+++++Download diagnostic data? (Y/N)? [Y]
+++++Stalking Horse v2.5f daemon corrupted. Reload from backup.
+++++Autopurge corrupted software (Y/N)? [Y]
*****INTERNAL: SIGANet
>>>>>[FROM: Cpl J S Karlsbruhn
TO: D J H Coppinger
CC: 1Lt L DiAnnio
We got what we could. It wasn't much.
+++++include data: stalking_horse.txt
We can pretty much forget any _real_ traces in-house, we'd need CSF, or
three or four of us working teamed, to break through this. They're using
some sort of offshore relay, at least, and the smartframes were all over
the Stalker before we'd even isolated that. The frames helped us some:
very tough stuff, not many guys around who write code that tight. Poor
old Stalky never had a chance.
No way to say who it was for sure, but there aren't many people whose
defences could spot the trace and frag it so fast.
+++++include list: possibilities.txt
>From their point of view it should look like a botched tracer attempt,
some half-smart street decker with a decent but not exceptional utility,
nothing more. If they do work out it was us, the list drops to the three
I highlighted.
Let me know if you need anything else. As long as you spring for the
overtime, I'm up for anything you need right now.]<<<<<
-- Corporal J S Karlsbruhn <23:40:32/07-02-57>
Strategic Intelligence Gathering Agency
