"Claudio Orlandi" <[EMAIL PROTECTED]> writes: >>> Converting this simple protocol to the active case is harder than >>> expected, and I'm working on it right now. >> >> Great, I'm looking forward to it! :-) > > Well, if you have a lot of spare time you can start some > preprocessing :)
Well, what are weekends but lots of spare time? > In particular, I guess that the active protocol will almost surely > need some commitment schemes. And to make them as efficient as we > can, we will probably use some elliptic curves over Zp with p around > 160 bits. Cool -- that sounds like a good opportunity to finally sit down and create a slow-but-simple elliptic curve library for VIFF. As far as I remember the NaCL people did not only do network stuff, right? So some Python code would provide a kind of specification for them to program against when they get started in the CACE project... > Isn't it cool that 160bits is at the same time the size we need for > security AND to avoid the overflows in the computation? :) It certainly is! :-) -- Martin Geisler _______________________________________________ viff-devel mailing list (http://viff.dk/) [email protected] http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
