LifeStir - Your Web Social Network DNA - social networking                           

Kernel Code Encapsulation + Encryption + Transaction Journaling: Concept Discussion - New Pervasively Ledgered Encryption Based Secure Network OS (PLEBS NOS)

Group Info

New Pervasively Ledgered Encryption Based Secure Network OS (PLEBS NOS)

New Pervasively Ledgered Encryption Based Secure Network OS (PLEBS NOS)

Proposal for a new OS based on the following requirements:


**Ledgering and journaling of IPC to enhance security.

**All IPC and data transfer sequences encrypted, with decentralized signatures en masse.

**No server caching, all communications via local and transglobal networking with caching at routers.

**Communications and processing with hardware encryption dependent.

**Completely Open Source to prevent ransom demands and back door formations.

**Independent decentralized committee to oversee development (no enterprise or bureaucratic agendas).


Check out the Sticky Forum Topics below for further information about PLEBS NOS, and please comment and criticize constructively.

David Underwood
David Underwood Mar 29 '16

Present day software is far too accessible to the public, allowing code manipulation and subversion. To date, obscurity was thought to provide adequate protection, this concept being made redundant by the proliferation of Open Source code.


Object orientated programming facilitates object encapsulation, pretty much like cells within the greater organism. Taking this analogy to the next level, encapsulated micro operations with different classes and functions will allow encrypted encapsulation, allowing only legal interactions with other non-aggressive micro operations or read/write data. All interactions would require signed encryption keys, preventing rogue and destructive interactions, very much in keeping with organic cell-cell interaction and foreign body rejection mechanisms. Yes, organic life certainly can teach software engineers a few things. 


Cell-Cell Communications & Interactions


Referring to the Information Hiding article in Wikipedia:

In his book on object-oriented design, Grady Booch defined encapsulation as "the process of compartmentalizing the elements of an abstraction that constitute its structure and behavior; encapsulation serves to separate the contractual interface of an abstraction and its implementation." The purpose is to achieve potential for change: the internal mechanisms of the component can be improved without impact on other components, or the component can be replaced with a different one that supports the same public interface. Encapsulation also protects the integrity of the component, by preventing users from setting the internal data of the component into an invalid or inconsistent state. Another benefit of encapsulation is that it reduces system complexity and thus increases robustness, by limiting the inter dependencies between software components.


PROPOSAL: One of the parameters for code interaction unlocking could be licencing compatibility. Enable a a verification system within each encapsulated micro code to check if the licence is compatible with the other encapsulated micro code they interact with. So a GPL 2 code snippet would disallow code interaction with an Apache Licence code snippet, for example. Extrapolating further, if the author of the code snippet requires monetary reimbursement for the code, this could be implemented within the verification system. Making this pervasive and highly granular might seem complex but by setting up all template encapsulated objects with code interaction verification systems with rules, it could be surmised that code snippets thrown into a processing pool would seek out other compatible code snippets and if monetary reimbursement is required, request is made to the user via a GUI. This would force the use of free as in beer code snippet licences, as paid ones would be a chore to use regularly. This also provides options for those who seek reimbursement to request monetary compensation if they want to go down this route.

It is clear that a highly componentized (as compared to a monolithic type) and heavily encapsulated kernel would benefit from the inherent safety of simplification of complexity. Couple this with encrypted component linking with journaling with a block chain type ledgering system, a truly reliable and safe kernel is possible.


The MUEN Separation Kernel is a rather succint implementation of the above concepts, encapsulating software code  within virtual boxes, allowing safe inter process communications and interactions.



The Forum post is edited by David Underwood Mar 30 '16
This topic is sticky
You need to be a group member to post.
web counter
web counter