VIFF

Hi Guys! Sorry bother you with something like this, but I was wondering whether there is a ceiling on the number of nested operations you can perform on a single variable i.e. (multiplications and comparisons). That is because even though I manage ... [More] to synchronize and shut down the runtime, my callback function is never executed. Right now I'm working with some matrices and executing something around 800 operations on the variable I'm trying to open. SO I thought that might be the cause. The following are the closing statements from my protocol. As I mentioned the sync and the shutdown are executed without problems.. but the callback function is never called and the process stays like in idle. opened_result=runtime.open(F[0][1]+one) opened_list = gather_shares([opened_result]) opened_list.addCallback(self.do_result) #syncronization process, executed only one time during the hole excecution print 'sync starting' runtime.schedule_callback(opened_list, lambda _: runtime.synchronize()) print "done sync" # connections between the players. runtime.schedule_callback(opened_list, lambda _: runtime.shutdown()) print "done shutdown" Any help would be gratly appreciated. Once again sorry bothering you guys during summer. Thanks in advance. Abdelrahaman Aly PhD Candidate - Engineering Sciences U.C.L - C.O.R.E [Less]

Hi - I spent a few hours updating viff to use recent versions of gmpy and Twisted. And, I submitted a pull request to Martin's bitbucket fork of the repo: https://bitbucket.org/mg/viff/pull-request/1/update-dependencies-to-recent-versions/diff As ... [More] the pull request mentions, I'm having some difficulty getting some of the tests to pass and running the included examples. In particular, when running the examples, I get the exception mentioned by Hongda in his email to this group in February: http://article.gmane.org/gmane.comp.cryptography.viff.devel/921 It seems to me that this exception could be related to a change in Twisted. But, after spending an hour looking at it, I found it beyond my ability to nail down. I'm excited to use Viff and would greatly appreciate help getting the tests and examples to run. Sincerely, Kyle [Less]

Hi, The repository is now up again. Best regards, Marcel On 02/07/13 09:28, Martin Geisler wrote:

Hi Mike <mikeazo <at> cableone.net> writes: to work and I cannot checkout the repository. Is there a time frame for getting this working? I don't know what is wrong with the Mercurial repository at hg.viff.dk. I don't have access to ... [More] that machine any longer after I stopped being a student at Aarhus. I've pushed the changesets that I had in my local repository to Bitbucket: https://bitbucket.org/mg/viff/ That is everything up to version 1.0 that I used for my dissertation. I hope that helps! [Less]

Yes, I used it for my dissertation in 2010 and it worked well then.

Hi Sashank, The website at http://viff.dk/ works for me. But you're probably talking about the Mercurial repository at hg.viff.dk which I see returns Internal Server Error. I once pushed some commits to Bitbucket, but I guess the mirror there is ... [More] outdated: https://bitbucket.org/mg/viff Does anybody else have a more recent version of the code? I'm afraid VIFF is no longer actively maintained by me and as far as I know nobody else is working on it. Maybe someone on the mailinglist can contradict me :-) [Less]

Dear Bharti, It is recommended to install the packages using the package manager of your operating system. If this is not possible, the gmpy source code can be found here: http://code.google.com/p/gmpy/downloads/list and the openssl source code ... [More] can be found here: http://www.openssl.org/source/ I think that the latest versions, gmpy 1.16 and openssl 1.0.1 should be fine because VIFF only uses a small part of their API. Best regards, Marcel On 03/04/13 17:10, bharti gupta wrote: [Less]