Arrow768 Posted February 27, 2017 Posted February 27, 2017 So to sum it up: The problem is, that it is way too easy to setup a hidden upload terminal anywhere on the station or the astroid. A scientist can easily print out the required boards and place a upload anywhere they want. The following has been proposed to resolve this issue and is worth looking into: Upload consoles need to be "activated" by two heads of staff before they can be used. Non-Standard and high risk modules need to be "authenticated" by two heads of staff before they can be used Bypassing the activation / authentication can be done with a emag DNA / Finger Print based auth Other abilities to subvert the AI if there is a reasonable amount of effort required to do so Being able to backtrace uplod console (Integrate it into the IT logging infrastructure maybe ?) The following has been suggested, but is not feasible imho: Requiring the HoS or the Captain to auth a upload console Making the protection bypassable with a multitool (No, the multitool is not a hacking device capable of bypassing software restrictions; Its a hardware manipulation tool) Restricting the upload z-level (With the new map, all z-levels should be able to hold any console. With the current map its a bit different, but since we get a new map soon, its not worth looking into that)
Surrealistik Posted February 27, 2017 Author Posted February 27, 2017 The ease with which a Command role can access and subvert in the upload core itself is also a problem, but yeah, the main issue is Sci being able to easily print upload consoles and freeforms, and upload anywhere without any authentication.
Recommended Posts