SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?


To: Scott C. Lemon who wrote (28124)9/15/1999 1:35:00 AM
From: Bearded One  Read Replies (1) | Respond to of 42771
 
> So I would have to think that all the data in my vault/safes would
> have to be encrypted and then some means of providing a key to
> selected outsiders for each specific attribute in my vault/safe
> would have to be developed.

As you know, with key management this can become a nightmare. So each attribute would be encrypted, and only I would have the key to "write" this attribute, and then I give rights to people to "read" the encrypted value, and then a key to decrypt it? So the second person I want to be able to read it gets the key ... now, in this scenario, when I change the value of the attribute how do I "revoke" the key from the first person if I want to limit their access? Do I change the key on the new value? Then I have to redistribute keys to the remaining people who are supposed to have the key ...


I think that this problem is addressed by public-key algorithms. The key is to encrypt using two keys, your private key and the public key of the person to whom you are sending the attribute.
Say I have an attribute A which I want Alice to be able to view. I use Alice's public key and my private key to encrypt A, and Alice can then view A with her private key and my public key. Or, more to the point, I keep a list of public keys of the people whom I want to allow to read attribute A and encrypt with the appropriate key + my private key when that person comes calling. If I want to revoke access for person X, I simply drop X's public key from my list.