Asher
Former Vent Rat
Image Source: N/A
Intent: To create a anti-slicing routine for turrets to ensure their complete loyalty to sentient overlords.
Development Thread: if/else/default
Manufacturer: DataSec
Model: v1.21.002 (Impenetrable Tortoise)
Affiliation: Approved Customers
Modularity: No.
Production: Minor
Material: Variables, constants and algorithms. Encryption Module Chips and also memory sticks for delivery.
Description:
The first in a long planned line of defense articles -- the DataSec Client-Server Turret Manager (or just The Tortoise as the ‘Basement Geeks™’ called it) was a solution to a rising problem that had been observed amongst the battlefields throughout recent history: Slicers.
The idea was simple. The company wanted to ensure that nations and companies who really valued their privacy also had the tools to protect such things in not just the physical realm but the cyberworld as well. DataSec therefor came up with the idea of having things go back to the basics.
Each turret (client) in a system was connected through cables to one central hub (server). This server was in charge of everything. The IFF protocols, the event triggers and what each individual client connected to the server did. Each and every single turret’s impulse, digit and decimal had to be managed by the server itself before the client was allowed to work which in return meant that the workload would be huge depending on the amount of clients that were connected to each hub.
This also meant that on the client-side of things they had to install special encryption modules within the turrets that requested heavily encrypted randomized passwords and orders from the server. Data chips were installed upon the motherboard of said turret to take care of the decryption while at the same time replacing the turret’s original brain with one that only had two tasks: Reporting to the server and performing the server’s returned orders.
That however also meant that if the the cable connecting a client to a server was cut or if the server was shut down somehow the turret would enter standby mode until the connection was fixed again.
Of course, the clients were hackable but all you’d really get out of it would be the heavily encrypted data that the server sent to the turret which effectively meant that by the time you had decrypted the (to you) useless information all you’d really be met with would be the incoming orders that the turret was to execute. This was however a good way block the server’s access to the turret which would in turn effectively shut it down due to a lack of orders.
So in short the DataSec C-STM was the first basis of a product that would see continued development throughout the years. This was merely the first publicly available product they’d launch.
Summary of Weaknesses:
Summary of strengths:
Primary Source: N/A
Intent: To create a anti-slicing routine for turrets to ensure their complete loyalty to sentient overlords.
Development Thread: if/else/default
-----------------------
Manufacturer: DataSec
Model: v1.21.002 (Impenetrable Tortoise)
Affiliation: Approved Customers
Modularity: No.
Production: Minor
Material: Variables, constants and algorithms. Encryption Module Chips and also memory sticks for delivery.
-----------------------
Description:
The first in a long planned line of defense articles -- the DataSec Client-Server Turret Manager (or just The Tortoise as the ‘Basement Geeks™’ called it) was a solution to a rising problem that had been observed amongst the battlefields throughout recent history: Slicers.
The idea was simple. The company wanted to ensure that nations and companies who really valued their privacy also had the tools to protect such things in not just the physical realm but the cyberworld as well. DataSec therefor came up with the idea of having things go back to the basics.
Each turret (client) in a system was connected through cables to one central hub (server). This server was in charge of everything. The IFF protocols, the event triggers and what each individual client connected to the server did. Each and every single turret’s impulse, digit and decimal had to be managed by the server itself before the client was allowed to work which in return meant that the workload would be huge depending on the amount of clients that were connected to each hub.
This also meant that on the client-side of things they had to install special encryption modules within the turrets that requested heavily encrypted randomized passwords and orders from the server. Data chips were installed upon the motherboard of said turret to take care of the decryption while at the same time replacing the turret’s original brain with one that only had two tasks: Reporting to the server and performing the server’s returned orders.
That however also meant that if the the cable connecting a client to a server was cut or if the server was shut down somehow the turret would enter standby mode until the connection was fixed again.
Of course, the clients were hackable but all you’d really get out of it would be the heavily encrypted data that the server sent to the turret which effectively meant that by the time you had decrypted the (to you) useless information all you’d really be met with would be the incoming orders that the turret was to execute. This was however a good way block the server’s access to the turret which would in turn effectively shut it down due to a lack of orders.
So in short the DataSec C-STM was the first basis of a product that would see continued development throughout the years. This was merely the first publicly available product they’d launch.
Summary of Weaknesses:
It required physical maintenance
Quantity =/= Quality and the more clients you had hooked to the servers the slower the reaction times got in the form of severe network lag which could cause turrets to shut down at random.
The server had to be one or several physical consoles dedicated solely to running the clients’ every single move.
The client could be hacked to prevent the server’s access to its clients though the procedure had to be be repeated once for each client said server had going.
If no data was received from the server within a 10 second interval the turret shut itself down.
Summary of strengths:
A client that kept unwanted intruders away from your network.
A way to make turrets exceptionally difficult to slice and turn on allies.
A server that can handle up to 6 turrets individually before the workload started taxing on it too much.
Primary Source: N/A
