Re: Object Oriented Crypto API
RC> anything without having to know anything about those formats at all. Yes. We need to be able to drop in new algorithms, because nobody knows what new attacks will be developed. RC> a Universal Resource Name (URN) for key identification. Perhaps RC> "key://keyserver.domain/keyid" would be better. Need to expand the concept of a key just a bit here. Your URL for keys needs to map to a hierarchy of keys that apply to different facets of a person's life, (casual vs. sensitive, personal vs. business) as well as to different encryption engines. The pubkey I have in the keyserver for the RSA algorithm will not work if you want to use the FOO algorithm instead. Rather than replicating the entire structure of keys for each new algorithm that comes along, there should be a standard protocol for requesting these various key types from the same "place". * I can't find where to put the milk in my "cereal" port. --- * Monster@FAmend.Com *
participants (1)
-
monty.harder@famend.com