Difference between revisions of "Privacy"
Line 1: | Line 1: | ||
− | + | [[Category:Glossary]][[Category:Nodal Concepts]] | |
− | + | The privacy concept uses a portion of its global bandwidth resource to distribute private keys over all available data streams. This resource comes from the support that the provacy concept gains from usage. | |
− | |||
− | |||
− | |||
# Method | # Method | ||
− | This | + | This privacy 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. | 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. | ||
− | # Organisational aspects requiring | + | # Organisational aspects requiring privacy |
*Logins and passwords need to be securely routed amongst peers | *Logins and passwords need to be securely routed amongst peers | ||
*Financial transactions and account balances must be trusted | *Financial transactions and account balances must be trusted |
Revision as of 06:26, 11 May 2006
The privacy concept uses a portion of its global bandwidth resource to distribute private keys over all available data streams. This resource comes from the support that the provacy concept gains from usage.
- Method
This privacy 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.
- Organisational aspects requiring privacy
- 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
- Available key properties/constraints
- Media its resided on (RAM, HDD, Removable etc)
- Peers its resided on
- Protocols its travelled through