You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we'd like to use this library to implement a secure multi party computation protocol for a paper. Looking at the source code, I stumbled over the djcs_t_share_decrypt method which needs the private key.
which says private key in the doc string, but actually takes a public key.
I've looked at the local_ecample.c and there paillier is used with the share_decrypt method and the public key as a parameter. Intuitively this seems to be the correct way to me, since share_decrypt is intended to be used to 'partially' decrypt a ciphertext with the secret key share which the auth server holds, right?
Is my understanding of the intended functionality wrong and there is a reason why djcs_t_share_decrypt needs a private key, while for the Paillier equivalent the public key suffices?
Thanks for the library :)
The text was updated successfully, but these errors were encountered:
If anyone stumbles over this: the fork at https://github.com/lemonviv/libhcs seemingly contains a fixed version of djcs.
I've also started my own fork where I've mainly fixed up some of the C++ interfaces https://github.com/robinhundt/libhcs and will likely also incorporate the fix for djcs.
Hi,
we'd like to use this library to implement a secure multi party computation protocol for a paper. Looking at the source code, I stumbled over the
djcs_t_share_decrypt
method which needs the private key.libhcs/include/libhcs/djcs_t.h
Lines 216 to 228 in 0e1deea
This is in contrast to the equivalent method for the standard Paillier implementation here:
libhcs/include/libhcs/pcs_t.h
Lines 362 to 374 in 0e1deea
which says private key in the doc string, but actually takes a public key.
I've looked at the local_ecample.c and there paillier is used with the
share_decrypt
method and the public key as a parameter. Intuitively this seems to be the correct way to me, sinceshare_decrypt
is intended to be used to 'partially' decrypt a ciphertext with the secret key share which the auth server holds, right?Is my understanding of the intended functionality wrong and there is a reason why
djcs_t_share_decrypt
needs a private key, while for the Paillier equivalent the public key suffices?Thanks for the library :)
The text was updated successfully, but these errors were encountered: