HElib is an open-source software library that implements homomorphic encryption. It supports the BGV scheme with bootstrapping and the Approximate Number CKKS scheme. HElib also includes optimizations for efficient homomorphic evaluation, focusing on effective use of ciphertext packing techniques and on the Gentry-Halevi-Smart optimizations.
Auto-generated FFI bindings greatly reduce the burden of keeping a 3rd party library up to date. I'm exploring creating a Rust crate that binds to HElib. It appears promising.
There are some utility functions that may assist creating a 'safer' Rust crate with low level access. Would such additions be in scope?
To have a fully safe Rust crate would appear (at this early stage) to require more intrusive changes. This will be known once I have several working examples. Alternatively, the risky interfaces could be made private. Would such changes be in scope?
Auto-generated FFI bindings greatly reduce the burden of keeping a 3rd party library up to date. I'm exploring creating a Rust crate that binds to HElib. It appears promising.
There are some utility functions that may assist creating a 'safer' Rust crate with low level access. Would such additions be in scope?
To have a fully safe Rust crate would appear (at this early stage) to require more intrusive changes. This will be known once I have several working examples. Alternatively, the risky interfaces could be made private. Would such changes be in scope?