When host A transforms the delta it does not transmit the transformed delta. It only sends the original (thus no need to re-sign). But, it does indicate at which version it applied the delta so that all the other hosts can replicate the transformation when they get the delta. Host A may also ADD it's own signature to delta, but it never removes host B's signature nor does it modify the data signed by the originating host.
-Tad On Mon, Feb 8, 2010 at 3:23 PM, Torben Weis <[email protected]> wrote: > Hi, > I just came across a situation where wave host B was sending a > submit-request to host A which hosts the wavelet. The submitted delta is > signed by host B. > Now host A figures it should OT transform the delta. > But it can't because it would have to re-sign the transformed delta with A's > certificate. But some host C (running FedOne) complains because it expects a > signature from B, because the author of the delta is a user of B. > Now what to do? Should A reject the delta and let B do the transformation? > This is not guaranteed to terminate, thus there must be a different way. I > just don't get it. > Any quick help would be highly appreciated, because I am stuck at this > point. > Torben > > -- > 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. > -- 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.
