RP Log: Computer Core Woes
| Roleplay Log | |
|---|---|
| Participants: | |
Location(s):
| |
Stardate:
| |
| 2023-07-06 19:03 | |
- == Shuttlebay Two <USS Phoenix NCC-170100-A> ==================================
- Shuttlebay Two is much smaller that its counterpart in the Saucer section of the vessel. This bay's primary purpose is for the recovery of launched fighter craft, the maintenance of those craft, and repositioning of the fighters into the launch tubes before launch.
- A large blast door that curves with the underside of the stardrive section covers the aft bulkhead. The door slides up and out of sight during landing operations.
- Bay doors are closed.
[Shulon's Commbadge] Incoming communication request from Worthington.
Shulon taps his commbadge.
[Shulon's Commbadge] Opening communications channel from Worthington.
Shulon says, "Chill"
[Shulon's Commbadge] Worthington says, "Captain. I had something to discuss with you. Something I want your opinion on related to the security of this ship given our current mission status. Are you alone or is your location secure?"
"Not exactly, there are easily a couple dozen people in here." Chill replies. "But there are a couple options nearby."
[Shulon's Commbadge] Worthington nods unseen, thinking. "There's a pilot squadroom right off the shuttlebay, if that's what you had in mind. There's no reason for anyone to be in there unless there's a mission briefing for flight personnel," he says.
"Or the launch tube", Chill replies. "But we can decide when you arrive."
[Shulon's Commbadge] Worthington says, "Yes sir. I shal see you shortly. Worthington out."
[Shulon's Commbadge] Worthington double taps his commbadge.
[Shulon's Commbadge] Connection from Worthington terminated.
Worthington arrives from Deck 25 - Port Corridor.
Shulon nods towards the starboard squad room.
- Squad Room - Starboard <USS Phoenix NCC-170100-A> ==========================
- The purpose of this compartment is to conduct meetings with flight wing crews before deployment. Stadium-style seating allows all the flight crews a vantage point to listen to and observe the front lower podium where the briefing is being conducted. A series of viewscreens are setup on the lower end of the compartment, for viewing and discussing battle tactics and flight group assignments. The podium is well lit by overhead panels, highlighting the insignia of the Federation emblazoned upon it, while the rest of the room is more dimly lit. There is an LCARS panel to the right of the door, with added functionality to assist in the proceedings.
Worthington arrives from Shuttlebay Two.
Worthington enters and performs a cursory sweep of the compartment. Then he faces the captain. "Sir, the issues with the ship's computer have given me thought. We do not know how long the malicious humanist code was in our systems. One other fact about our computers, is that they communicate with one another. I am specifically talking about the computers on our auxiliary craft. Given that when they sync with the mothership, they transfer a variety of information, including data uplinks, sensor, comm, and nav data. What's the chance that the humanist program could have propogated on to any or all of our auxiliaries? It's a question I would pose to you and to Gordon, as I believe it is important to insure that all of our computer systems are clear of this program."
OOC: Shulon rolls his Computer Programming: Success by 57.
"They do share data, and the nature of the uplink does assume some trust between the two systems, but it still wouldn't be trivial to infiltrate a system externally, even through the uplink. It would take some serious hacking skills." Chill replies, "But, there may still be a risk. What do you propose?"
Worthington considers. "The things I remember most about the humanists and their afinity for computer systems involved networking and automation specifically. We were able to sweep the main core for malicious code. I suggest we do the same with each of our auxiliaries. We're not using them right now, so it's a perfect opportunity to sweep them for any malicious programming. If we find anything, we could isolate that craft and ground it until the matter is rectified. If we don't find anything, we're still better off for verifying that nothing was there in my opinion sir," he concludes.
Shulon says, "Part of the issue however, and Gordon can correct me here, I don't think he was able to isolate the malicious software. That's why the re-image was necessary. The only solution may be to re-image all the auxiliaries as well."
Worthington considers that, pondering. "And if the auxiliaries were infected in any way, then there's a decent shot we may not have a stable image aboard," he says, pondering. "It's a sticky situation. On the one hand, there could be nothing wrong at all. On the other, we could have compromising software in all our systems and think that the issue has been solved." He thinks further. "Do we have any examples of previous humanist automation code that has been used? For example, Europa I believe may have had some of it, the vigilents they controlled definitely did. It could be something to contact the Corps of Engineers about. Would a sample of the type of code they used help us to isolate similar code in our systems?" he queries.
OOC: Shulon rolls his Computer Programming: Success by 41.
"We re-imaged the Phoenix's computers based on the Hadfields. If the Hadfields was compromised, then there would be no change." Chill says, "Sample code might help, but if it was a different author, it would have different characteristics to it, making matching all that much harder. The computer might be able to do it, given enough time, but, that's assuming it doesn't know to skip hostle code."
Worthington nods, pondering. "I'm not a computer expert myself sir. I know enough to do what I need to, but not too much advanced coding," he says. He thinks. "What if we had several samples of similar code from different authors, but designed to perform similar functions. Could that help to isolate the effect based on comparison?" he asks.
"Once a system has been compromised, its really difficult to isolate the changes. Its part of the reason for the re-image." Chill replies, "There might be indicators of the compromise, depending on how skillful the malicious actor is, but as we've seen, they are very skilled. Even if you can identify there is harmful code, the only recourse is again, the re-image."
Worthington nods. "And the re-image must come from a source that is not infected," he says. "That's the other issue."
"Right, but it may potentially be far less painful just to re-image everything, than try to find out if they even need re-imaging." Chill replies.
Worthington nods. "I agree there sir," he says. "The only question remains. Where do we get that stable, non-infected image."
"We may already have one." Chill replies, "We won't truly know unless it acts up again."
Worthington nods. "I guess we'll wait and see sir," he says. "We'll just have to keep a careful eye on everything.
Shulon smiles, "We certainly will." He adds, "I don't want to dismiss your idea though, its good to be thinking of other avenues of attack. If engineering has the bandwidth, we could consider re-imaging the auxiliaries. It might be worth doing some research on the matter yourself too. To see how we could find malicious code in the cores."
Worthington nods. "I'll do my best sir. Will need to chat with any computer experts we have on hand," he says. "I won't rest easy until these conspirators are under lock and key sir."
Shulon nods slowly, "Lock and key."
Worthington smiles. "Thank you for your time sir. I will keep you apprised of any developments via secure channels. The XO and I have talked, and official reports are too easy to trace for someone with the computer skills involved in this sir."
Shulon says, "You can send a coded message to the Corps of Engineers too. Gordon may have done so already, so check with him first. But your idea of asking them if they have encountered this is a good one. It may give them information they didn't already have as well."
Worthington nods. "I will confer with him before doing so," he says. "We've worked out a long range comms protocol for data transmission then?" he asks.
"Not for direct visual communication, but for coded messages, yes, they should work. It might be a few hours, maybe even days delay." Chill replies.
Worthington nods. "Understood sir. It'll be done," he says.
Shulon's antennae lead the way back to the shuttlebay.