[viff-devel] VIFF needs at least 3 players always?

2010-10-07 Thread Kyung-Wook Hwang
Hello, This is Kyung Hwang from Columbia University again. I have another question. Does Viff always need at least 3 participants? It seems to me it does. I modified beginner.py for two players because that file was simplest to modify, but when I ran the two players, I got the following errors:

Re: [viff-devel] VIFF needs at least 3 players always?

2010-10-07 Thread Mikkel Krøigård
Citat af Kyung-Wook Hwang kwhw...@ee.columbia.edu: Hello, This is Kyung Hwang from Columbia University again. I have another question. Does Viff always need at least 3 participants? It seems to me it does. That depends on the runtime you use. If you are using the default passive security

Re: [viff-devel] VIFF and random numbers

2010-07-06 Thread Ivan Bjerre Damgård
It is not good to use the wrong kind of PRG, it should be fixed as soon as possible. But do we know that os.urandom will be OK on any platform, or is this OS -dependent at the end of the day? - Ivan On 06/07/2010, at 15.22, Thomas P Jakobsen wrote: VIFF itself as well as most protocols

Re: [viff-devel] VIFF and random numbers

2010-07-06 Thread Mikkel Krøigård
Indeed it should satisfy those properties. Say if you Shamir share something, the adversary might get t shares in order. If it can guess the next bit with non-negligible advantage, this will completely break our claim that the adversary has no information on the secret. Luckily it should

Re: [viff-devel] VIFF and random numbers

2010-07-06 Thread Marcel Keller
Thomas P Jakobsen wrote: The urandom is os-specific: This function returns random bytes from an OS-specific randomness source. The returned data should be unpredictable enough for cryptographic applications, though its exact quality depends on the OS implementation. On a UNIX-like system this

Re: [viff-devel] VIFF and random numbers

2010-07-06 Thread Thomas P Jakobsen
I agree that tests should be reproducible. But it is also very important to use a cryptographically secure PRNG. I don't know whether these two requirements can be satisfied by the same number generator. If not, the best solution is to have two modes of operation: - A test mode where the

Re: [viff-devel] VIFF reactor

2010-04-30 Thread Joel Pettersson
Marcel Keller mkeller at cs.au.dk writes: Hi Joel, Is it still necessary to run `viff.reactor.install()` as described in http://www.mail-archive.com/viff-devel at viff.dk/msg00657.html in order to utilize the VIFF reactor? - If so, would it be possible to fix that? I don't see

Re: [viff-devel] VIFF reactor

2010-04-29 Thread Marcel Keller
Hi Joel, Is it still necessary to run `viff.reactor.install()` as described in http://www.mail-archive.com/viff-devel@viff.dk/msg00657.html in order to utilize the VIFF reactor? - If so, would it be possible to fix that? I don't see a good way to that, for the following reasons: - To change

Re: [viff-devel] VIFF reactor

2010-04-29 Thread Martin Geisler
Joel Pettersson joel...@kth.se writes: Hi everybody, Is it still necessary to run `viff.reactor.install()` as described in http://www.mail-archive.com/viff-devel@viff.dk/msg00657.html in order to utilize the VIFF reactor? - If so, would it be possible to fix that? - If not, then the

[viff-devel] VIFF 1.0 released

2009-12-14 Thread Martin Geisler
Hi everybody! On behalf of the VIFF Development Team, it is my pleasure to declare that we have reached VIFF version 1.0. The current code is useful, flexible and unlikely to change radically. Please download it here: Tar/GZ: http://viff.dk/release/viff-1.0.tar.gz Tar/BZ2:

[viff-devel] VIFF 1.0 this weekend

2009-12-10 Thread Martin Geisler
Hi everybody, I would like to release what we currently have in VIFF as version 1.0 this weekend. The code has not evolved very much the last year, and releasing version 1.0 now will fit nicely with the reports we're writing for CACE and with my own dissertation :-) As preparation for that, I've

Re: [viff-devel] VIFF 1.0 this weekend

2009-12-10 Thread Håvard Vegge
And mine is here: http://daim.idi.ntnu.no/masteroppgave?id=4559 Put it anywhere you like! håvard atl...@stud.ntnu.no wrote: Siterer Martin Geisler m...@lazybytes.net: Hi everybody, I would like to release what we currently have in VIFF as version 1.0 this weekend. The code has not evolved

Re: [viff-devel] [viff-commits] viff: Generate_config_files:Added support NaCl implementation of...

2009-10-29 Thread Janus Dam Nielsen
Some good old-fashioned code review coming up... :-) Great! /rev/736ad1d97024 changeset: 1361:736ad1d97024 user: Janus Dam Nielsen janus.niel...@alexandra.dk date: Wed Oct 28 14:53:51 2009 +0100 summary: Generate_config_files:Added support NaCl implementation of Paillier.

Re: [viff-devel] viff 0.7.1 question

2009-10-21 Thread Sigurd Torkel Meldgaard
Hi, I hope this question is not a bother to you. No, not at all I was trying to test viff-0.7.1, as I executed generate-config-files.py, I got the error ¨ImportError: No module named viff.config¨. Im not sure how to fix this problem. Most likely viff is not yet on your PYTHONPATH

Re: [viff-devel] VIFF benchmarks

2009-02-05 Thread Martin Geisler
Thomas Jakobsen thomas@gmail.com writes: Hi Thomas I've written a VIFF application that should make it easy to create, run and visualize benchmarks for VIFF protocols. I've put some changes to it here -- it's only style changes in order to make it more pythonic :-) Please pull from this

[viff-devel] VIFF 0.7

2008-09-21 Thread Martin Geisler
I'm very happy to announce the release of VIFF version 0.7: Tar/GZ: http://viff.dk/release/viff-0.7.tar.gz Tar/BZ2: http://viff.dk/release/viff-0.7.tar.bz2 Zip: http://viff.dk/release/viff-0.7.zip Exe: http://viff.dk/release/viff-0.7.win32.exe The changes since version 0.6 are:

[viff-devel] VIFF 0.6 released!

2008-05-28 Thread Martin Geisler
I am happy to announce the release of VIFF version 0.6: Tar/GZ: http://viff.dk/release/viff-0.6.tar.gz Tar/BZ2: http://viff.dk/release/viff-0.6.tar.bz2 Zip: http://viff.dk/release/viff-0.6.zip Exe: http://viff.dk/release/viff-0.6.win32.exe Executive summary of the changes since

Re: [viff-devel] viff: Switch to prss_share_bit_double in comparisons.

2008-05-27 Thread Martin Geisler
Ivan Bjerre Damgaard [EMAIL PROTECTED] writes: Quoting Martin Geisler [EMAIL PROTECTED]: .. but this makes viff.test.test_runtime_comp.ActiveToft05GreaterThanEqualTest go into what looks like a never-ending loop?! You you have a better solution, then I'm all ears! :-) What is wrong

Re: [viff-devel] viff: Switch to prss_share_bit_double in comparisons.

2008-05-16 Thread Ivan Bjerre Damgaard
Quoting Martin Geisler [EMAIL PROTECTED]: .. but this makes viff.test.test_runtime_comp.ActiveToft05GreaterThanEqualTest go into what looks like a never-ending loop?! You you have a better solution, then I'm all ears! :-) What is wrong with just doing a single normal secure

Re: [viff-devel] viff: Switch to prss_share_bit_double in comparisons.

2008-05-15 Thread Tomas Toft
Hi Martin Geisler wrote: viff-devel@viff.dk writes: Hi everybody, I don't know how many of you follow the commits to the VIFF repository? Would anybody be interested in a mailing list for it? Anyway -- the latest commit is this: http://hg.viff.dk/viff/rev/5dd8c277268c changeset:

Re: [viff-devel] VIFF unit tests

2008-02-14 Thread Martin Geisler
Janus Dam Nielsen [EMAIL PROTECTED] writes: I think that having parametrized tests is good, however I just wanted to point out that defining the parameters in the Runtime class/object might not be suffienciently expressive to what we want. We might would like a kind of grouping/system of

Re: [viff-devel] VIFF unit tests

2008-02-13 Thread Martin Geisler
Janus Dam Nielsen [EMAIL PROTECTED] writes: Does it make sense to run all unit tests with the same configuations of players and thresholds. That is, for all protocols p, is p executed with x players and threshold t is p welldefined? Well, no, not in general. If you write a protocol for seven

Re: [viff-devel] VIFF 0.3 has been released!

2007-12-28 Thread Martin Geisler
Janus Dam Nielsen [EMAIL PROTECTED] writes: Hi Janus That is great news! As expected, the time per multiplication stayed constant when I varied the number of multiplications -- with the parallel scheduling there is a huge difference between doing 100 and doing 1000 multiplications (a