>> Why? If you're interested in hiding the content of the transfers
> because of government persecution of Christians in some countries, I
> think the US has cryptographic export restrictions for most of those
> same countries.
Chris, for good or ill, I believe PGP is available pretty much everywhere in
at least 64 bit. If not other international developers have encryption
technologies too. The real difficulty is source identification, not contents
so much. If they want to persecute, all they need do is watch for file
transfers from your source, and pick up offenders regardless of what was
downloaded. A better solution would be a form of encrypted file sharing that
lets anyone be a server and client both.(Where have we seen that before?)
Protect rights management the same way. Allow users to download and maintain
authentication keys for other users, but not use them or have access to them
directly. I am thinking of a cascadable confirmation on query protocol that
specifically protects against queries of all users even if the database and
source code for the program falls into the wrong hands. At the same time an
internet like routing protocol needs to be able to trace data routes back to
source, and bogus ping traces designed to decipher routing information need
to be detectable, and killable, or better, sent on a fools errand. It would
be nice to be able to failsafe the system and leave everything turned on for
users durring periods of extreem persectution, but that might conflict with
copyright management, especially dot net style enough to make it infeasable.
Michael