@Sirin: Perform a Scan
19:52, Today: Starfleet, on behalf of Lieutenant(jg) Sirin Norn, rolled 12 using 2d6+3 ((3,6)). +1 tricorder STRONG SUCCESS

The tricorder bypasses the security lockouts on the cloaking device and you get a solid analysis...

Tell me something interesting about the cloaking device, and I'll tell you two more useful pieces of information.

---

@Kotar: Perform a Scan
19:53, Today: Starfleet, on behalf of Kotar Krenn Sogh, rolled 5 using 2d6 ((2,3)). +1 tricorder

Choose:

(1) FAIL Mark 1XP

Hu'tegh! The security programming of the cloaking device locks out your tricorder.

or...

(2) Edge Bump WEAK SUCCESS

Well, well... isn't this interesting...

I'll tell you something useful about the cloaking device

"How is... OH! That's not possible... but.... Oh my... but what about the quantum... this is..... AHA! I see."

He did some rapid mental calculations, checked on his padd, did a scan. No wonder they weren't at all concerned about the power systems being overstressed.

The device didn't need to interface with a power supply. It had its own.

The really humbling thing was that this cloak didn't really represent any new crazy principles of engineering: just very rare and expensive components employed in unexpected amounts. It was the kind of reverse purpose engineering that left engineers such as himself in awe.

It is good once in a while to be so utterly humbled in one's own specialty. I think I am ready for the briefing now.

This is a modular disposable cloak. It has its own power supply based on obscure unique chemical systems and huge internal finite batteries. No power is needed, but when it's done the cloak is DONE and will melt into slag.
This message was last edited by the player at 06:43, Tue 08 Mar 2022.

Kotar taps his tricorder once or twice and slides his eyes sideways at Norn, who seems to be getting excellent readings. Anger bubbles beneath the surface, but is forced relentlessly down.

"My device is unable to bypass the security protocols," he grates. "But it seems you have learned something of interest. We should return to the Ready Room and share the knowledge."

He's not looking forward to squeezing through the access passages on the way back to the main section of the ship.

OOC: He'll take the fail. Trust the dice.

On Sirin’s tricorder:

@Kotar, @Iren, @Sirin - gathering here is as good as anywhere!

Intrigued to be working on a multi-faceted technical problem with his new crew-mates, Kotar is enthusiastic.

"We have an enemy, and we shall conquer!" he declares as the three officers start to divvy up the tasks of isolating and eradicating the worm.

Moves: Perform Scan (?)

@Kotar - you still have 1 Hold, so no need to scan. You can ask a question or add a detail that makes your work progress

From Main Bridge —>

Putting his knowledge of the computer systems to work Iren offers his ideas.  “We must strategise!  I suggest we create a honeypot.  A virtualised copy of a subsystem to lure the worm!  When it infiltrates the honeypot we suspend execution and begin with the disassembler!  I much prefer dissecting code to dissecting biologicals”

I've asked about the virus, but I didn't get any response to my scan, so I'm just going to make something up.

"All Starfleet systems are encoded with basic security and operations protocols hard-coded as a backup in case of computer failure. It's how the ship can function despite computer failure.

The obvious solution, and frankly, one I recommend we take once we're clear of this,  would be to completely reformat the core from scratch and install a hardwired iso chip with manually entered codes. I can lock changes to the chip, so unless someone wants to steal the iso core and carve a new one, they won't be able to change the command codes. This will prevent all sorts of sabotage workarounds.

Unfortunately, this will shut down the ship for at least 6-8 hours. Possibly longer as there are security upgrades and CPU issues ongoing as well. Something to consider, however, once we avoid any minor catastrophes for more than 24 hours straight.


Grand strategies preserve him. This ship was a mess. And the science officer's idea was insane. How would dissecting a single copy of the worm help? They had infected files. They need a purge the system of the worm, not just chop up the code.

The honeypot idea.. it's quite good, actually. We might be able to reverse engineer a counter virus to infect the worm.

It's designed to resist deletion no matter what we do, but we might be easier to infect the worm with a virus of our own to stop it from doing anything.

Then we can purge the systems at our leisure when we have time to shut the computers down.


He tried considering the potential advantages and problems of the idea.

Well, there was this:



Then this was my response...





Yes, exactly. Hold spent.

Within a few hours, your small but dedicated team is able to mimic the algorithmic vulnerabilities in a duplication of the deck 12 power distribution relays. When the honeypot is exposed to the worm, the code immediately replicates and infects the subsytems. Once it is established in the mimic system, you can see how the worm rewrites the source code introducing minor variations that make the secondary systems susceptible to failure.

A few isolation partitions later and you have the worm trapped in a system you control. The worm is invasive and difficult to detect, but not particularly adaptive. From within your partitioned systems, you can recreate the worm and experiment with different variations to it's code as you seek a vulnerability.

"That's interesting," Lallios observes, "Why doesn't the worm move into new subsystems on the ship? It is clearly capable of replication, but is so far limited to power distribution relays, the communications subsystems and the shuttle craft inertial dampeners. I wonder why."

Someone feel free to explain what is similar about these subsystems that makes only them vulnerable to the worm.

Of course there is no possibility of shutting down the ship for a lengthy period while answering a distress call.

Iren puts his research skills to use, identifying the optimum parameters for the computer queries.

“The main attack mode of the worm relies on a feature of revision 17.3 of the A23-gamma sub-processor unit - all of which are meant to have been removed from service.  However, the original systems on the Phoenix are of the right vintage.  Replacements might have been overlooked in the hurry..”  he muses.  “Computer.  Engineering database query.  Identify all systems employing A23-gamma sub-processors of revision 17.3.“

“A23-gamma units installed in power distribution relays, communications, and astrometrics.  Details on console”

“Include shuttle craft and auxiliary systems in query.”

“The following shuttlecraft have A23-gamma sub-processors of revision 17.3”

Iren looks satisfied - perhaps self-satisfied,  “Gentlemen I think we have it.  Can we replace the sub-processors in those areas before we arrive at the Horizon’s location.”
This message was last edited by the player at 15:21, Sun 03 Apr 2022.

Kotar enjoys working with his new companions. They seem very competent. He does his best to keep up with them and makes one or two observations of his own that contribute to the overall process of isolating the worm and understanding how to remove it from the ship's systems. It is this kind of teamwork with other species that he had hoped to find in Starfleet and it seems to be working out as well as he had hoped.

He makes a formal salute to both men as they finalize their approach.

"Well done, gentlemen. I think the Captain will be pleased."

Norn looked relieved. "A most optimal strategy and we've worked out the logistics brilliantly if you will forgive my Zakdorn modesty. I cannot see any flaws, at the very least."

This represented the first time he'd really worked with the others. It looked like they'd been blessed with capable minds that worked well together.

Given how serious the situation was, this was most fortunate.

If I might make one more suggestion. Why don't we do the replacements ourselves?

There aren't that many processors, though they are still in key areas.

If the saboteur is still aboard, it may be beneficial if they still think their sabotage has worked, at least for now.

Or am I just being overly cloak and dagger?

Iren considers the suggestion.  “You wish to bypass the engineering crew?  I suppose it can be done.  Provided the replacement process is not too complicated - you will have to walk us through it if we are to carry out the work.”

"It should be just a matter of removal and replacement in the specific systems.

If we leave this out of the standard engineering log, no one will know without checking the circuits manually, or a level 3 diagnostic, which I would have to approve."

And the less people who knew about this below the senior rank, the better. Best let any saboteur think they'd succeeded.

The computer displays a list of systems that are compromised.

Astrometrics Lab distribution relay overload buffer - Deck 9 - Access Panel 256

Sickbay secondary overload buffer #4 - Deck 12 - Jefferies Tube 12-Alpha, junction 2

Ship's Lounge Replicator surge protector - Deck 10 - replicator bank 2

Subspace amplifier secondary power regulator - Deck 23 - Primary Communications Workstation, access panel (rear)

Shuttlecraft Mockingbird - Deck 4 - Starboard inertial dampener, floor access panel (main)

"In that our plan is to refit these systems without arousing any suspicions of those who planted them -- if they are indeed still on the ship," growls Kotar, "might I suggest we spend the remainder of our current journey running surprise drills with our respective crews.

"We will have them disassemble and 'repair' systems harmed in mock battles as part of a training exercise to familiarize the crew members with their new vessel. This is the reason we will give out. And one of us will be present at each of these particular locations to actually remove and replace the suspect subsystem.

"It is always best to lead by example. And it will actually be good for the crews to have to work together under pressure."

“An interesting thought.  But I do not believe that it would work well with my department.  Perhaps it is better also if we do not conspicuously do the same thing.“ Iren responds, considering possibilities.  “The communications systems would seem to be in your purview, astrometrics in mine.  The shuttle may safely be taken out of use.  Mr Norn, do you think you can cover the sickbay and the replicator?”

"That is wise. I hope that personally adjusting sickbay way will somewhat improve the Doctor's mood.

In addition, the thought of either of those systems being compromised is quite troubling."

“Then that is what we shall do.  Mr Norn, shall we go get the replacement units?” Iren asks.

Jump straight to installing the replacements?

—> To Stellar Cartography
This message was last edited by the player at 21:22, Fri 08 Apr 2022.

Good with me, unless you need more to keep it going…

sounds good!

Kotar puts his plan for surprise drills for his direct report staff into place. He creates a half dozen simulated damage reports as if inflicted by combat, or solar flares, or asteroid impacts, etc. He sets his crews to making swift repairs, swapping out "damaged" components to restore the vessel to full functionality as quickly as possible. He makes sure to include many more systems than the ones identified as compromised. He also makes a contest of it between different watches and observes their individual performances closely, issuing ongoing encouragement and praise. At the end of the exercise, he gives a detailed breakdown of his evaluation of the various individual's skill levels to the Captain and spends a few minutes with each person who reports to him in positive reinforcement. He wants to build a team he can trust and who trusts him.

He even has a small awards ceremony in the mess to declare the third watch crew the overall winner of the exercise.

Working with the ship's quartermaster, he makes sure that the replaced units are set aside for "repair" and then extracts the specific components they had identified as infected with the worm, placing them in a secure locker, letting Norn and Thatyil know what he has done and giving them both the code to the locker.

At first the detachments look at each other quizzically, wondering what you have in mind and perhaps a bit hesitant about your direct Klingon demeanor. But as you explain the readiness drills, and the contest, their faces light up and they get to work.

Team one speeds off to repair the damaged transporter buffers after an encounter with a subspace anomaly.

Team two immediately gets to work swapping out power modules in the deflector to reverse the damage suffered from a Romulan bird-of-prey.

The tractor beam is the focus of the victorious team three. You can't help but declare them the winners after they conduct a complete overhaul on the ion manifolds, which consequently improves performance by four percent.

Trying not to be too obvious, you pay particular attention to the repair teams working on the communications array. It would be incredibly bad luck if one of the saboteurs was unknowingly assigned to these repairs. Fortunately nothing seems amiss as the crews replace the A23-gamma sub-processor unit with a new unit running upgraded software.

Qapla'!