Hi Tad, I read that as saying client signatures are not supported.
The FedOne implementation does what the sandbox does: signing is for federated servers who must trust each other or nothing can happen. Clients must trust their server (or they should find another server). This means that clients are not currently able to do signing or encryption. I personally think one way to (ab)use the current architecture is: 1. Run your own federated server 2. That means you'll need a certificate for your server 3. If you want more than signing (such as encryption), you can use the type of the blip to specify that the data is not "plain text." David > Does this mean that client signature of delta's is supported in the > sandbox but not FedOne? > > -Tad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
