![]() | |
|
The pattern Spike was using to match on was one he put together from the trace file. It held more than enough examples of responses that he just pieced together. All he had to do was separate the data from the headers and control bits in order to reach a replica of the result file. If he found a file with the same pattern, he'd have the link he needed. Many of the systems Spike was analyzing were quite slow. His pattern matching technique required that he siphon off a fair percentage of CPU from each host machine. It was taking a lot longer than he planned. But at 5:14 a.m., on what had become Tuesday morning, a hit was recorded. Spike had made it about halfway through the alphabet and was just beginning to question his own methods when it happened. He had preset response routines for the hit event which would immediately assess the status of the current host system and then review the site overall. These routines were designed to determine his own safety status and gather information about associated processors which he could evaluate later. Upon completion of the assessment procedures, the "PatternMatched" function automatically moved Spike out to a safe, open network host bringing with him the site assessment data and a copy of the file where the pattern match occurred. Spike was out within a second of the pattern match and the data file made it 30 seconds later. Spike moved himself through a maze of locations to scramble his tracks and returned to MicroLabs. He sent Nancy an e-mail letting her know of his success and safety. He then began to research the information he had acquired.
![]() ![]() ![]()
ISYS Idea System, Inc. designed and implemented the Spike Webb (tm) site, including all content and artwork.
Copyright © 1995 ISYS Idea Systems, Inc. All rights reserved. Reproduction in whole or in part in |
|