<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Jun 8, 2014 at 9:40 PM, Dirk-Willem van Gulik <span dir="ltr"><<a href="mailto:dirkx@webweaving.org" target="_blank">dirkx@webweaving.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 8 Jun 2014, at 11:47, xor <<a href="mailto:crypto@idlecore.com" target="_blank">crypto@idlecore.com</a>> wrote:<br>
> I'm a programmer, I need a way to have several people sign the same<br>
> message, <br></div></blockquote><div>..... </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> <a href="http://theory.stanford.edu/~dfreeman/cs259c-f11/finalpapers/aggregatesigs.pdf" target="_blank">http://theory.stanford.edu/~dfreeman/cs259c-f11/finalpapers/aggregatesigs.pdf</a><br>
><br>
> I couldn't find however a single implementation, I couldn't find one in<br>
> openssl, nss, or anywhere else. Does anyone know of a decent<br>
> implementation? Does anyone know if there is even a standard?<br>
<br>
</div>Firstly - a million private keys is a very large number - even in todays internet day and age <br></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
title = {Accountable-subgroup Multisignatures: Extended Abstract},<br></blockquote><div> </div><div>Yes....</div><div>Lots of keys is a lot of data and a lot of key look ups and verification (slow).....<div>
<div>
</div></div></div><div><br></div><div>If you are talking about a million keys you quickly will find you</div><div>are no longer in the world of email. I commonly assemble a message</div><div>with quality images and more only to find that I fill up the mail box</div>
<div>of one or more friends or I encounter my service limits.</div><div><br></div><div>Clearly you need a secure place for the document shelf for the document</div><div>to live while it collects signatures. You must keep the signatures </div>
<div>and data isolate. The collection of signatures needs to be signed</div><div>so joe-random-badguy cannot insert himself. </div><div><br></div><div>With a million your tool may need to manage (cope with) revocations often...</div>
<div>
<br></div><div>If the document is more than one screen you need to allow those that</div><div>sign time (perhaps weeks) to view, read etc. and then sign. </div><div><br></div><div>Signers need to verify the document they sign and did sign is the exact one that they</div>
<div>reviewed. Recall Radar putting a stack of paper in front of Col. Potter with a </div><div>"ringer for Clinger" in the pile. This may prove the hardest part...</div><div><br></div><div>Authority must be managed as must invitations so trust is not lost.</div>
<div>If trust is only validated by a majority of strangers and automated army</div><div>of robots with pseudo users could assert and dominate the validity</div><div>or invalidate the document.</div><div><br></div><div>Validation implies/mandates revocation... I might agree today learn something</div>
<div>tomorrow and thus wish to withdraw my signature. Later might get back on board</div><div>when the flaw is fixed or I learn more. </div><div><br></div><div>Note the web (HTML) has no state so these atomic operations are difficult.</div>
<div><br></div><div>Me ... I would look at enhancing Mercurial, Git or another distributed source control</div><div>system and add a sign off with signature feature. If you get it right I can see value</div><div>and quick user adoption especially if you can embody a signature tree for use in</div>
<div>review and accept processes.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div>-- <br><div dir="ltr"> T o m M i t c h e l l</div>
</div></div>