Hi Nat,<br><br>in those cases where public keys cannot be used, because parties are not known yet, maybe using PBE (password based encryption) with random generated pass could fit this need. <br>Those passwords could be stored bound to the contract and delivered to the party after a challenge has been passed (f.ex auth process).<br>
<br>Best regards<br><br>Dave<br><br><div class="gmail_quote">2010/6/25 Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I had a talk with Hide yesterday.<br>
We were talking on how to preserve the privacy of the end user among<br>
bunch of services.<br>
<br>
The agreement we had was that we should encrypt the portion of the<br>
agreement specific to each server with different symmetric keys, then<br>
encrypt the symmetric keys with respective server's public key and<br>
OP's public key.<br>
<br>
We are still discussing over the cases where parties are not<br>
determined at the time of the proposal and disclosing the parties to<br>
other parties are privacy risk.<br>
It is a bit challenging.<br>
<font color="#888888"><br>
--<br>
Nat Sakimura (=nat)<br>
<a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br>
<a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
_______________________________________________<br>
Specs-cx mailing list<br>
<a href="mailto:Specs-cx@lists.openid.net">Specs-cx@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-cx" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-cx</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>David Garcia<br>CTO<br>Tractis - Online contracts you can enforce<br><a href="http://www.tractis.com">http://www.tractis.com</a><br>--<br>Email: <a href="mailto:david.garcia@tractis.com">david.garcia@tractis.com</a><br>
Skype: deiffbcn<br>Blog: <a href="http://blog.negonation.com">http://blog.negonation.com</a><br>Linkedin: <a href="http://www.linkedin.com/in/davebcn">http://www.linkedin.com/in/davebcn</a><br><br><br>