Welcome to Star Trek Simulation Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

LcdrBrown

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LcdrBrown

Contact Methods

  • ICQ
    0
  1. Log: Lt. Brian Brown As Brown sits at his computer console waiting for his R.O.A.C.H. program to find the source of who or whatever is affecting the station’s computers, he decides to pull up a log he had written about R.O.A.C.H. several years ago. ********************************************************************* 9901.30 U.S.S. Melbourne, Ens. Brian Brown… Duty Log I recently developed a surveillance program for use in Star Fleet Security. The program, R.O.A.C.H. (RemOte Access Computer Hack) was activated onboard the Melbourne for testing. The program takes control of all communications systems, internal and external sensors, monitors, cameras, force-field systems, doors, and computer security. Using these tools, the program's built in minimal A.I. follows a set of parameters to control systems. During the constable test, an individual was told to proceed to break down a door by any means necessary. The R.O.A.C.H. program detected this happening, and as the “criminal” made his escape, force-fields were erected around the individual, and he was beamed directly into the brig, where the force-field was put in place and he was imprisoned. All without a security officer tracking him down or making an arrest. The next test, was more than just a test, it was an actual attack, and the whole thing went awry. This is where the flaw in the R.O.A.C.H. program lies. Another vessel was hacking into our ship’s computer when R.O.A.C.H. detected this happening. R.O.A.C.H. did what it was supposed to. It tracked down the intruder and locked him out. But, then it did something it was not designed to do. An unfortunate flaw in the A.I., vengeance. R.O.A.C.H. spread itself to the other ship’s computer, taking it over. It downloaded the entire database, and any “upgrades” it had received as a result of the transfer, and the program began to grow. It became more than just a surveillance program. It became a digital Gestapo. The offending vessel was then destroyed. No count-down. Just destroyed once its usefulness was up. With no way to control R.O.A.C.H. we were doomed to be destroyed. With the help of our Chief Engineer, he and I developed at this point what would be considered an anti-virus. R.A.I.D. (Remote Access Inhibitor Download). We inserted this program into the computer, and as expected, R.O.A.C.H. went to attack the program, and make it part of its digital matrix. However, R.O.A.C.H. was deleted on our ship’s computer by R.A.I.D. I have 2 data chips that I will carry with me from now on. These two chips will someday come in handy again. On one chip, is the original, pure version of R.O.A.C.H., which can be safely used as long as it is not used to defend against hacking from another vessel or base. The other chip is the anti-virus. R.A.I.D. R.A.I.D. can’t be in any computer system where you want to use R.O.A.C.H. A copy of both will be sent to Star Fleet HQ in San Francisco for analysis and development if they see it useful. ****************************************************************** Brown took a deep breath and began to record his new log. 0407.30 Reluctantly, the situation has warranted the usage of the R.O.A.C.H. program. We have no control over our computer systems and we don’t know why. Our efforts have produced nothing in finding a cause for the problems. Therefore, HD, mr. Zhu and myself have decided to go ahead with the R.O.A.C.H. program. I am worried that if this is an off-station intruder, that the program will again spread itself. On the Melbourne, it was only the one other vessel in the vicinity. Here, we have hundreds of vessels that could be infected with R.O.A.C.H., and several planetary computers that could be infected within a matter of 24 hours. I have been working on a self-spreading version of the R.A.I.D. program that would provide a cure, should R.O.A.C.H. get out of hand. I only hope it doesn’t come to that. End Log…… -Lt. Brian Brown Chief Science Officer