Difference between revisions of "Privacy"

From Organic Design wiki
(Method)
(Security is a component of Storage&Distribution)
Line 1: Line 1:
 +
# How does security fit in to the nodal model?
 +
Security is really a component of Storage & Distribution, because its about connections between remote peers and their ability to authenticate each others identities. So part of S&D's bandwidth, storage and processing resource is dedicated to security.
 +
 
# Sessions
 
# Sessions
 
Every context of execution can be considered as a session in the nodal model. Any context can adjust its security aspects with logins and logouts. Even peers use the same authentication process for routing their own secure information such as access information or currerency.
 
Every context of execution can be considered as a session in the nodal model. Any context can adjust its security aspects with logins and logouts. Even peers use the same authentication process for routing their own secure information such as access information or currerency.

Revision as of 11:21, 18 February 2006

  1. How does security fit in to the nodal model?

Security is really a component of Storage & Distribution, because its about connections between remote peers and their ability to authenticate each others identities. So part of S&D's bandwidth, storage and processing resource is dedicated to security.

  1. Sessions

Every context of execution can be considered as a session in the nodal model. Any context can adjust its security aspects with logins and logouts. Even peers use the same authentication process for routing their own secure information such as access information or currerency.

  1. Method

This security is handled with any of the standard algorithms such as DES or AES, but using the inherent organisational methods to generate and maintain a diverse population of private keys so that any context of information can be made arbitrarily secure dynamically and independently. A small portion of bandwidth is dedicated to random connectivity for creating keys with more diverse properties, and for finding new efficient routes.

When a context requires its connected streams to be authenticated, it generates random content along with a randomly selected key it shares in common with the peer. The context expects a hash of the random content and private value associated with the key. This can happen any number of times and can also occur independently of the context directly between peers.

  1. Organisational aspects requiring security
  • Logins and passwords need to be securely routed amongst peers
  • Financial transactions and account balances must be trusted
  • Users personal information must be kept private
  1. Available key properties/constraints
  • Media its resided on (RAM, HDD, Removable etc)
  • Peers its resided on
  • Protocols its travelled through