>>> As far as I can tell, all wavelet updates >>> (ProtocolAppliedWaveletDelta) are signed by the federation host and >>> not by the federation remote or the actual client. > > All deltas are signed by the wave server to which a client submits the > delta, regardless of whether that wave server is the host of the > wavelet. (see WaveServerImpl.submitRequest(final WaveletName > waveletName, ProtocolWaveletDelta delta, final SubmitResultListener > listener) in FedOne). In the current architecture, clients trust their > service providers (i.e. wave servers) to correctly handle their data. > The federation protocol deals with trust between servers.I expect one > day we may support user signatures, but not at this point.
Ok, that clear's up one misconception :-) >> However I can point out that a number of people on the sandbox have been >> requesting the ability to sign/encrypt content so the recipients >> can verify the validity of the data. > > Signing is supported, though there are a few bug fixes in the pipeline. 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 -~----------~----~----~----~------~----~------~--~---
