deWulf Corporate Democracy Turn 132

Fiction by Sylvester Wrzesinski

Moderator: Xveers

deWulf Corporate Democracy Turn 132

Postby Xveers on Fri 22 Dec 2017 12:58

Sebb Gloval Museum Station
Fenris Orbit
deWulf Corporate Democracy

"Hello and yes, welcome! Come now, plenty of room!"

"So glad you could all be here to join us. I know that it's been a lot of work for us to get this all working, but I'm happy, yes, very happy to welcome you all to the official grand opening of the Sebb Gloval Museum Station. I know we've all suffered through the opening speeches and the unsealing ceremony, so let's go have a quick tour of the first three piers, and then we can get on to the buffet. Don't worry, I know where your priorities all are!"

"Yes, all the docked ships will be open for tours after the buffet. Yes, you can queue up before hand, but you'll still have to wait."

"Ah, yes, on to our first pier. This is is our exploratory pier. A little sparse right now, but we think it's best to allocate a good amount of space right off the bat. Right now we have the dWMS Augen, and the dWMS Denkfaul. The former is being refitted back to her original Mk1 condition as of her original commissioning, and the Denkfaul is in her current Mk3 configuration. We're quite lucky to have two Augen class ships; most of them are being sent to the breakers, but the deWulf Navy was kind enough to donate both hulls for our use."

"Yes, we'll be doing some interpretive centers and the like on both ships, focusing on different aspects of space exploration. We're looking at having planet-side survey on Augen, and space surveying on Denkfaul, though when we get one of the command survey ships, we'll be moving the planet side survey over to her instead. Moving on."

"Pier 2 is our first of two First Contact War piers. On one side we have a Slingshot-class, the dWMS Catapult, and a Hauptmann-Class, the dWMS Hauptmann. We're particularly proud of getting Hauptmann. She's only seen minimal upgrades since the First Contact War, and the majority of her systems are either period manufacture or period accurate. We're also scheduled to be getting the dWMS von Braun, the deWulf flagship for the second half of the war, but she's still undergoing decommissioning at the Mittelspanung yards. We won't be seeing her till early next year at the earliest."

"Pier 3 is probably our most controversial pier at present. Right now it has a Strelets-Class Light Cruiser, but we're working with a memorial fund from Sintilla to see if they can find a wreck of a Storvin or Ostrova-Class Frigate. It's going to be a long process, but we're also hoping to get a Berlenko-Class Destroyer as well. A few of them survived the war as scrap salvage, and we're seeing if any of them are still reasonably intact. As it is, we have a few containers docked with various components and interpretive exhibits, but we feel it's important to show both sides of the conflict."

"At present we have only the exhibits for three piers at the moment. Pier 4 is slated to be the Binary War pier, and Piers 5 and 6 will be used for visiting ships on port tours, at least until we have more exhibits to put on display. Now, with that all done, let's head to the central dome for the buffet. Once we're all done with lunch, we can go down the pillar and see the small craft exhibits."
Xveers
Vice Admiral
Vice Admiral
 
Posts: 733
Joined: Wed 15 Jul 2009 02:26
Location: New Westminster, BC, Canada

Re: deWulf Corporate Democracy Turn 132

Postby Xveers on Wed 03 Jan 2018 04:22

Deep Space
Piraeus-Elysium Warp Line
Elysium System

Even at this stage of the war, Elysian navy forces had chosen not to defend their warp points. A sensor watch was kept, modified freighters holding at a far enough range to give them a chance to escape but still able to watch the warp points. Away from the planet and its defensive fire, deWulf ships had shown their ability to sweep any warp point clear.

But that comprimise between sensor coverage and the ability to escape meant that the warp point wasn't perfectly covered. True, any starship, or even any gunboat would be spotted and identified. But drones were small enough that they could slip in and out and not be spotted.

And thanks to both the captured battlecruiser, as well as significant amounts of spare parts and salvage from Dave's World, the deWulf were ready to try a new technique against the Elysian navy. A single drone slid in through the warp point, the wormhole barely flickering as it passed through. Slowly stabilizing after transit, its scanners locking on to the watching freighter.

Too far away to be detected by its sensors, the drone carefully aimed its communications laser at the waiting freighter. Built from equipment left behind on Dave's World, the laser triggered no alarms. On the right frequency and with the correct initial handshake protocols, the freighter's automated systems opened a communications link with the "friendly" drone. The freighter interrogated the drone, and provisionally accepted the access codes while it waited for further confirmation.

Here the deWulf showed just how carefully they had studied Elysian technology. The initial comm request was carefully malformed, taking advantage of a subtle design oversight in the communications preprocessor. All it took was a carefully formed data header to cause part of the communications preprocessor to lock up, which in turn timed out the authentication request. That lack of response told the preprocessor to fully accept the outdated access codes, as no alarm had been triggered. With the communications link authenticated, the drone messaged that it had routine navigational updates. What it actually sent was something far different.

Once in the suborned communications preprocessor, the uploaded data packet unfurled into an invasive worm, slowly taking up more and more processing cycles as it listened to the data system it was a part of. Its first act was to "confirm" its access by reinitializing the locked up part of the preprocessor, and then presented its new "up to date" access codes. These updated codes were duly sent to the main server, which then confirmed the validity of the permissions it had already granted.

RTN-220 PROCESSING CYCLE DETECTED
XERTOS DATA LOOP ARCHITECHTURE IDENTIFIED
QUERYING SECONDARY DATA ROUTER

deWulf scientists had identified several flaws in the network architechture found of Elysian ships, and with an access point, they were finally able to put their knowledge to use. One of the largest weakpoints was that most system maintenence was managed through the secondary data router. In principle, it was a good idea as it kept the main data loop free for operational traffic. In practice, it meant the left hand of the network didn't always know what the right was doing. Worse, its memory management was built for speed first, and security second. After all, a hostile agent would need physical access to insert something into the data loop.

After thirty seconds of sniffing, it had identified the locations where permissions were stored in active memory:

IDENTIFY NAVIGATIONAL UPDATE V1588.8a
QUERY NAVIGATIONAL FIX 005-883-480-586
UPDATE NAVIGATIONAL FIX 005-884-480-586

All it took was a single burst of data, and a single bit switched value before the secondary router knew what was happening. Instructed to update an obscure navigatonal reference (a resource-poor kuiper moonlet in the Elysian system), the data overflowed from one memory reference into a neigboring bit, and the "navigational update" found it had complete access to all hardware in the secondary data loop.

With complete official access, the worm then backdated its own access, making its access completely above board. While this wouldn't stand up to any real scrutiny, it took advantage of one final weak point in the data loops. While the primary loop was carefully monitored for possible intrustions, the secondary data loop relied on external access codes and authentications for its security. By definition, if you had access, you were authorized.

This little bit of circular logic was its true weak point.

The worm then roamed the local network, hunting for any loose bits of information. Recent messages, navigational orders, personal notes, news reports and briefings. It hoovered it all up, compressing the data ruthlessly before bouncing it back to the waiting drone. It's work done, the worm quietly folded back in on itself, changing the date-stamps on some of the navigational files to preserve its cover identity. Once it received confirmation that the data was secure on the drone, it revoked its own network access before flagging itself for routine deletion (and triggering a garbage management routine in the process).

The process took less than 90 seconds, and the drone quietly slunk back through the wormhole to its eventual rendezvous, the freighter none the wiser.
Xveers
Vice Admiral
Vice Admiral
 
Posts: 733
Joined: Wed 15 Jul 2009 02:26
Location: New Westminster, BC, Canada


Return to deWulf Universe

Who is online

Users browsing this forum: No registered users and 2 guests

cron