http://blog.gmane.org/gmane.comp.cryptography.viff.patches hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.cryptography.viff.patches/161 <pre> -------- Original Message -------- Subject: [PATCH 1 of 1] Added computation-id option Date: Wed, 04 Aug 2010 12:17:43 -0000 From: Thomas P Jakobsen &lt;tpj&lt; at &gt;cs.au.dk&gt; To: mkeller&lt; at &gt;cs.au.dk CC: ttoft&lt; at &gt;cs.au.dk References: &lt;patchbomb.1280924262&lt; at &gt;dhcp-11-67-32.daimi.au.dk&gt; # HG changeset patch # User Tomas Toft &lt;ttoft&lt; at &gt;cs.au.dk&gt; # Date 1280227043 -7200 # Node ID 7c45463151f482ff75bbd877dad3509e8f9cb3c9 # Parent e7b2fe7eb75319e2f60cc292b0d68fe568d394ab Added computation-id option. This changeset adds a command line option to VIFF allowing users to specify a computation id. Prior to this changeset, any computation involving pseudo-random secret sharing (which for the time being boils down to computations done with the PassiveRuntime) could only be run one time using the same set of VIFF player configuration files. If more than one computation was executed with the same set of configuration files, the security of the system would be broken. With this changeset, multiple computations can be run securely with the same set of configuration files as long as each computation is run with a unique computation id. diff -r e7b2fe7eb753 -r 7c45463151f4 viff/runtime.py --- a/viff/runtime.pyThu Jul 29 15:58:52 2010 +0200 +++ b/viff/runtime.pyTue Jul 27 12:37:23 2010 +0200 &lt; at &gt;&lt; at &gt; -536,6 +536,10 &lt; at &gt;&lt; at &gt; "multiple times on the command line; the first will " "override host and port of player 1, the second that " "of player 2, and so forth.") + group.add_option("--computation-id", type="int", metavar="ID", + help="Set the (positive, integer) ID for this " + "computation. Must be unique to ensure " + "security.") try: # Using __import__ since we do not use the module, we are &lt; at &gt;&lt; at &gt; -551,7 +555,8 &lt; at &gt;&lt; at &gt; deferred_debug=False, profile=False, track_memory=False, - statistics=False) + statistics=False, + computation_id=None) def __init__(self, player, threshold, options=None): """Initialize runtime. &lt; at &gt;&lt; at &gt; -585,7 +590,12 &lt; at &gt;&lt; at &gt; self._needed_data = {} #: Current program counter. - self.program_counter = [0] + __comp_id = self.options.computation_id + if __comp_id is None: + __comp_id = 0 + else: + assert __comp_id &gt;0, "Non-positive ID: %d." % __comp_id + self.program_counter = [__comp_id, 0] #: Connections to the other players. #: </pre> Marcel Keller 2010-08-04T12:28:21 http://comments.gmane.org/gmane.comp.cryptography.viff.patches/159 <pre>Here's a patch that allows users to specify player host and port numbers via the command line. If theres no objections, I'll push this change into VIFF in a couple of days. Regards, Thomas </pre> Thomas P Jakobsen 2010-04-13T18:15:22 http://comments.gmane.org/gmane.comp.cryptography.viff.patches/157 <pre># HG changeset patch # User Thomas P Jakobsen &lt;tpj&lt; at &gt;cs.au.dk&gt; # Date 1263974081 -3600 # Node ID 2324d01c74e2c35b5bb6cb4d7bda1304a376b066 # Parent efa1983063d62a8115949a7e63d5ad4e5a23a791 Added option to avoid retrying to connect if socket is already in use. In some situations it turns out to be more convenient to have VIFF throw an exception rather than keep retrying to connect to a socket with exponentially increasing delays. This is now possible using the new command line parameter --no-socket-retry. diff -r efa1983063d6 -r 2324d01c74e2 viff/runtime.py --- a/viff/runtime.pyThu Jan 14 11:36:13 2010 +0100 +++ b/viff/runtime.pyWed Jan 20 08:54:41 2010 +0100 &lt; at &gt;&lt; at &gt; -525,6 +525,9 &lt; at &gt;&lt; at &gt; help="Collect and print profiling information.") group.add_option("--track-memory", action="store_true", help="Track memory usage over time.") + group.add_option("--no-socket-retry", action="store_true", + default=False, help="Fail rather than keep retrying " + "to connect if port is already in use.") try: # Using __import__ since we do not use the module, we are &lt; at &gt;&lt; at &gt; -1068,6 +1071,8 &lt; at &gt;&lt; at &gt; try: runtime.port = listen(port) except CannotListenError, e: + if options and options.no_socket_retry: + raise delay *= 1 + rand.random() print "Error listening on port %d: %s" % (port, e.socketError[1]) print "Will try again in %d seconds" % delay </pre> Thomas P Jakobsen 2010-01-20T07:56:34 http://comments.gmane.org/gmane.comp.cryptography.viff.patches/154 <pre># HG changeset patch # User Thomas P Jakobsen &lt;tpj&lt; at &gt;cs.au.dk&gt; # Date 1263939336 -3600 # Node ID 0b1e6cf3f57efe5a3b320897da636a6e2ebb2bdf # Parent efa1983063d62a8115949a7e63d5ad4e5a23a791 Added option to avoid retrying to connect if socket is already in use. In some situations it turns out to be more convenient to have VIFF throw an exception rather than keep retrying to connect to a socket with exponentially increasing delays. This is now possible using the new command line parameter --no-socket-retry. diff -r efa1983063d6 -r 0b1e6cf3f57e viff/runtime.py --- a/viff/runtime.pyThu Jan 14 11:36:13 2010 +0100 +++ b/viff/runtime.pyTue Jan 19 23:15:36 2010 +0100 &lt; at &gt;&lt; at &gt; -525,6 +525,10 &lt; at &gt;&lt; at &gt; help="Collect and print profiling information.") group.add_option("--track-memory", action="store_true", help="Track memory usage over time.") + group.add_option("--no-socket-retry", action="store_false", + dest="socket_retry", default=True, + help="Fail rather than keep retrying to connect " + "if port is already in use.") try: # Using __import__ since we do not use the module, we are &lt; at &gt;&lt; at &gt; -1060,18 +1064,21 &lt; at &gt;&lt; at &gt; connect = lambda host, port: reactor.connectTCP(host, port, factory) port = players[id].port - runtime.port = None - delay = 2 - while runtime.port is None: - # We keep trying to listen on the port, but with an - # exponentially increasing delay between each attempt. - try: - runtime.port = listen(port) - except CannotListenError, e: - delay *= 1 + rand.random() - print "Error listening on port %d: %s" % (port, e.socketError[1]) - print "Will try again in %d seconds" % delay - time.sleep(delay) + if options and options.socket_retry: + runtime.port = None + delay = 2 + while runtime.port is None: + # We keep trying to listen on the port, but with an + # exponentially increasing delay between each attempt. + try: + runtime.port = listen(port) + except CannotListenError, e: + delay *= 1 + rand.random() + print "Error listening on port %d: %s" % (port, e.socketError[1]) + print "Will try again in %d seconds" % delay + time.sleep(delay) + else: + runtime.port = listen(port) print "Listening on port %d" % port for peer_id, player in players.iteritems(): </pre> Thomas P Jakobsen 2010-01-19T22:18:59 http://comments.gmane.org/gmane.comp.cryptography.viff.patches/141 <pre>Hi friends of VIFF, This pathcbomb contains three contributions 1) I have made it possible for a player to send and expect data from him self. This simplifies the implementation of the broadcast protocol I have implemented for the Orlandi runtime 2) An implementation of the Orlandi runtime. I have decided not to include the code for the commitment scheme yet, since it uses propriatary code 3) A refactoring and improvement of the benchmark.py application Please review the code. -- Janus </pre> Janus Dam Nielsen 2009-10-06T08:09:50 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.cryptography.viff.patches