Re: [viff-devel] New passive multiplication protocol
Claudio Orlandi [EMAIL PROTECTED] writes: (I send your off-list reply back on track) Where is a description of the new protocol? Use the source, Luke! :-) It is just the normal passive multiplication protocol where I have cut away all the work that is not needed: we only need 2t+1 shares to recombine, so only 2t+1 players will even calculate and broadcast shares. The others simply wait on the 2t+1 shares. The good question is now how we can get the best of both worlds so that the case with (n, t) = (3, 1) remains fast. What about if n=3 then RunOldProtocol else RunNewProtocol? :) Wrong syntax: if n=3: RunOldProtocol() else: RunNewProtocol() :-) But apart from that then you're right -- maybe that is what we have to do if we can find a nice way to do it. -- Martin Geisler VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/. ___ viff-devel mailing list (http://viff.dk/) viff-devel@viff.dk http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
[viff-devel] [issue71] Allow self-sending
New submission from Martin Geisler [EMAIL PROTECTED]: At some point it became illegal to send data to oneself, and so the code looks like this in several places (this is from open): if peer_id == self.id: d = Share(self, share.field, (share.field(peer_id), share)) else: d = self._expect_share(peer_id, share.field) I think the rationale for disallowing self-sending is that the players have no ShareExchanger for themselves, and so one cannot _expect_data or sendData to oneself. But it should still be possible to clean up the code by handling this in one central place. Maybe like it is done in _exchange_shares. -- keyword: design messages: 263 nosy: mg status: unread title: Allow self-sending type: wish VIFF Issue Tracker [EMAIL PROTECTED] http://tracker.viff.dk/issue71 ___ viff-devel mailing list (http://viff.dk/) viff-devel@viff.dk http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
