Hi Presently: > a, b, c = rt.shamir_share(input)
Potential future > if rt.id == 1: > # do something for P1 > elif rt.id == 2: > # do something for P2 > else: > # do something for P3 > > Alternatively one could write three different source files, but this > does not scale to protocols with more players. While I really feel that it's necessary to let the parties perform different actions, I'm not sure that there's an elegant way to get around the problem. Symmetry is lost, so they *are* trying to do something different, so of course they need separate program-paths somehow. In the general case this is unavoidable. I think one simple solution to break the symmetry could be just to provide the possibility of having one party share a value. x = rt.shamir_share(input, player_id) Party player_id plays the role of dealer, while all others simply receive their share. As receivers have to provide a dummy input it's not as pretty as I'd like, but alternatively the programs have to be different, which is also bad. Are there really other problems than sharing (and opening a shared value towards only one party)? Just my 2 cents /Tomas _______________________________________________ viff-devel mailing list (http://viff.dk/) [email protected] http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
