Hi all,
As you may or may not know, running the same VIFF program more than
once using the same set of player configuration files is insecure when
the runtime relies on pseudo-random secret sharing. This is the case
for e.g. the PassiveRuntime.
This is not a bug, but rather a consequence of the w
Thomas P Jakobsen writes:
> Hi all,
>
> As you may or may not know, running the same VIFF program more than
> once using the same set of player configuration files is insecure when
> the runtime relies on pseudo-random secret sharing. This is the case
> for e.g. the PassiveRuntime.
>
> This is no
New submission from Thomas P Jakobsen :
Currently, VIFF uses a pseudo-random number generator with weak security
properties (Mersenne-Twister). We should rather use a cryptographically
strong prng.
See discussion at
http://article.gmane.org/gmane.comp.cryptography.viff.devel/834.
--
On Thu, Aug 12, 2010 at 12:06, Martin Geisler wrote:
> Would it not be fairly easy to let each of the players secret share a
> random integer, add all the shared numbers, open the result, and use
> that as the computation ID? That is, automate this so that you don't
> have to agree on a certain c
