SECURITY - LeFreq/Singularity GitHub Wiki

Security of the p2p, open system is handled by data redundancy (a la FreeNet) and snapshots of the system: what objects are present and the version number of the object. For user data, data is stored like a cache elsewhere on behalf of everyone, compressed/encrypted with a datetime stamp or version number, do that you can do 95% recovery or more with a little effort.

As people create their own objects or update them, they are cloned to peers on a schedule related to how many peer-changes occur, how much availability of peers there are, etc. System-level updates can occur the same way, as an updated system object transfers to other nodes, pretty soon their node security will update all other nodes with the same name (SINGULARITY:OBJECTn) and the global network is made up-to-date. This requires extreme care that there is truly new wisdom for the system to encode in the Singularity objects otherwise the system can also get a global FAILURE if some update prevents copying nodes or executing the code across the system.

%uptime: how often in some time-period the system was online.

A system-wide SET ENTER command sets a list of nodes which can enter objects. Beyond that, an object-level exclusion list, says who is excluded from entering a particular object.

See also ComputerSecurity.