Kim Laine

It should work fine, so I suspect something else is wrong. Maybe the header files are not correctly included? Did you add `native/src` to your project in the include directories?

It sounds like you did everything correctly. Would it be possible to share the project?

Is there a reason why you commented out the SEAL header file from your includes? Maybe that's the only reason it doesn't work?

SealPIR depends on an older version of SEAL that uses a different kind of key switching technique. The current approach requires you to have at least two primes in your...

When you create new parameter sets, the buffer allocation sizes change totally. SEAL memory pool only reuses memory allocations if their sizes match exactly. The justification for that is that...

Very good suggestion again from you. We'll need to test this, do some benchmarks, and figure out whether it makes sense. Changing the hash function is in principle really easy,...

Thanks for suggestion. We'll leave this issue open and will get back to it after the next release. One issue is that this kind of seeded secret key is not...

There is already a pretty easy way to achieve this by using a PRNG seed as the key and then use that PRNG only for setting up the KeyGenerator as...

I'm wondering why you have two directories called `build` within each other? Could you try taking a fresh clone of the repo and try again with `cmake -S . -B...

Your project is not finding the GSL headers. I would recommend using CMake to build your project in which case it should automatically work. Otherwise you’ll need to manually add...