-
Notifications
You must be signed in to change notification settings - Fork 160
Question about sending BinaryIO of context and pubKey to another party #175
Comments
Due to some reasons, write to file and read from file is not considered. |
@DylanWangWQF I would have to try this out myself, but if I remember right, you can't mix and match contexts. if you use the old context instead, does it work? |
@boland25
So, it seems that the generated pk and sk using these new and old context cannot be used to encrypt and decrypt. |
@boland25 @deanthomasson HElib is usually built against GLIBC, while Alpine Linux is based on the MUSL C library. And for Thanks in advance! |
@DylanWangWQF I have not dug deep enough into the Alpine docker implementation of it as that was done by another team member but its building off of cmake and using the gcc compiler. There must be some sort of wrapper that is done under the hood that makes it happen, but I am not sure of this completely. As for your bug, I have someone working on this to try and re-create it, and should have an answer to you shortly. Thanks for your patience! |
@boland25 |
@DylanWangWQF can you please provide the source code that you were using where you ran into the issue so we can re-create? |
Hi, @boland25 For the current version of HElib, we cannot do like this: In the traditional way, we can But now, I don't understand the way of releasing memory since we must build the context using the Sry for my noise. |
@DylanWangWQF thanks for sending that over. I have someone working on re-creating your test. Bear with us, as he is only on the project part time so will take a bit to get a response. In regard to your last question, have you checked out the tutorial folder? There are a few different tutorials in there that might help, and you can use |
@boland25
|
Hi, @boland25 @deanthomasson .
I have a question: when I generate a new context by reading from stringstream, these two context should be equal. But if I encrypt the vector using the oldContext.publickey, then decrypt it using the newContext.seckey. It failed due to different context.
Could you give me some suggestions?
The text was updated successfully, but these errors were encountered: