The Locker Box concept

Published on 11 February 2026 01:15 PM
The Locker Box Computer
Cruel Computer Designs


Since, in general, the technological solutions the society uses are in one way or another insecure, I came up with the idea of the Locker computer. What is The Locker Box? Locker Box Computer is a fully functional, integrated, stable, consistent, multi-purpose Unix based workstation and a server designed for consumer/business/military market. It is supposed to be able to be an office machine, it will be suitable for web browsing, every day computing, computer graphics or even entertainment. It comes with a promise of never spy on the user and always stand by his side, the promise of loyality. Why BSD Unix? The BSD license allows the code to become proprietary, the most of the OS is supposed to be proprietary in the end for sake of the security of the user and security of the Locker Box Computers intellectual propriety. The Locker computer is supposed to provide maximum data security and user anonymity for the population. It is supposed to take unauthorized access to user data or metadata away from absolutely ANYONE, government or other bandits. The Locker project aims to bring an integrated, out of the box fully functional, universal unix computer unit, similar to other computers but in orientation of end user online security, internal data security, anonymity and privacy standards. The military model could find multiple uses in a conflict situation.

Features of the concept:

• Full ZFS disk encryption by default, key stored in a TPM chip (will require ZFS auth mechanism modification)
• Out of the box, preconfigured VPN for all users (Fleet), single web site, all nodes world-wide available after extra payment, full services access, you're getting, well, servers and whatnot ... (which will require a lot of networking infrastructure world wide, chaining vpns should be possible, will require a fleet of servers, yeah... lets talk about the Fleet... what's new in Fleet Department...) Fleet is supposed to have a multiplatform client
• Development of GUI for components like package management, packet filter, jails, filesystem management, service management, VPN management, network, nfs, smb management
• When it comes to the hardware platform, I’d base it on ARM or RISC and rather avoid using x86 based platforms
• The system will require a process of software and hardware selection and then detailed audit
• System updates get extenssive audits from all sides, security/stability/consistence and additional platform software can be added via future jail gui for sake of system structure
• One of the future features I see is a data kill switch. Lets say in combat condition a machine could be captured and even while being encrypted sent for analysis and possibly exploited for data. A bailout data killswitch could solve this issue. It would require a custom nvme device with a custom controller and a system drivers where predefined chunks of space on nvme memory contain containers that hold encrypted data. When “pulling” the switch, the controller would allow to instantly zero whole areas of the the drive, the predefined areas that hold the containers. That method wipes crucial data without destroying the whole system and bricking the device, this way the device can be still in use in meantime. That’s one of the ideas for future.
• Before wiper drives get manufactured, software kill switch is possible, kernel rapidly terminates the containers, the container key gets replaced with random key that intantly gets forgotten. Poor man's solution, however fully doable in software without need of specialized hardware. Yeah, kill switches are cool tools for military/espionage operations but they could also save a regime target from terrible fate in prison
• I suspect the first unit to not be too excessively priced due to generic construction of components of the initial design, the Fleet gonna be funded by the Fleet Membership plan
• Everyone's leet until they meet the fleet