Janus Dam Nielsen writes:
>> Also meaning there is a slight delay in the next release. I don't
>> know if VIFF has a release schedule or something similar?
> I don't think there is a release schedule, but at least once every
> three months or so.
I tried making a release last December, but nothi
Hope you had a good vacation.
Yes, very nice!
I did not have any time yet to replace or test the code with in
VIFF, this is mainly due have some other task that need some
attention to.
Ok.
Also meaning there is a slight delay in the next release. I don't
know if VIFF has a release sche
Hi Marc
I am back from vacation and looking forward to the next release. Have
you tried to replace the current uses of Paillier in VIFF with your
code?
On 03/08/2009, at 11.11, Marc Makkes wrote:
Hi Janus,
The inclusion of multiple gmp.h and time.h is indeed a sloppy. This
will
fixed
Hi Janus,
The inclusion of multiple gmp.h and time.h is indeed a sloppy. This will
fixed in the next release. I'm currently working on there key generation
and some additional speedup. I hope to release it at the end of the
week. In addition I have some for key extraction and recomputing
methods.
Hi Claudio,
Yes, It takes 496 msec on my machine. For timing i used the following:
python -m timeit -s 'from pypaillier import generate_keys, encrypt' \
-s 'pk, sk = generate_keys(2048)' \
-s 'm = 98723498' \
'encrypt(m, pk)'
python -m tim
Hi Marc,
Let me see if I understood the way you measured: it takes 496 msec on
average to do an encryption with your code, right?
Claudio
On Fri, Jul 10, 2009 at 10:18 AM, Marc Makkes wrote:
> Hi Janus,
>
> I think that I'd have reached the stage where you can test my code, but
> still lacks som
Hi Marc,
Thank you for your email.
I will have a look at the code, when I get back from vacation two
weeks from now.
On 10/07/2009, at 10.18, Marc Makkes wrote:
Hi Janus,
I think that I'd have reached the stage where you can test my code,
but
still lacks some basic checks and is still
Hi Janus,
I think that I'd have reached the stage where you can test my code, but
still lacks some basic checks and is still prone to timing attacks and
is basically the same viffs current implementation, with some additional
speedups. So consequently, it code should only be used for testing pur
