fully-homomorphic-encryption
SEAL
fully-homomorphic-encryption | SEAL | |
---|---|---|
19 | 6 | |
3,455 | 3,391 | |
0.3% | 0.8% | |
7.0 | 0.0 | |
about 2 months ago | 7 months ago | |
C++ | C++ | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fully-homomorphic-encryption
-
What are the current hot topics in type theory and static analysis?
Secure computing. This includes Fully Homomorphic Encryption AKA FHE, of which there is a language/compiler which just got released and Google's older FHE compiler. FHE is probably more "compiler" than "type system", e.g. Google's compiler works on C++. Also Security Type Systems which include Oblivious data structures and Oblivious ADTs.
-
Ask HN: Should we follow what impresses us?
I don't have any advice for you, but I do work on homomorphic encryption at Google and we have an FHE compiler project [1] (though it is likely going to change a lot in the coming year). I happen to have a math PhD, so the transition to this field was not a huge stretch, but before that I worked in supply chain optimization for data centers, and just decided this was too exciting to pass up.
[1]: https://github.com/google/fully-homomorphic-encryption/issue...
-
Spiralโs Homomorphic Encryption โ Is This the Future of Privacy?
+1, and some compilers already exist to do that for you. See, e.g., Google's compiler (which I work on). https://github.com/google/fully-homomorphic-encryption
-
Weโre Christian Mouchet, Jean-Philippe Bossuat, Kurt Rohloff, Nigel Smart, Pascal Paillier, Rand Hindi, Wonkyung Jung, various researchers and library developers of homomorphic encryption to answer questions about homomorphic encryption and why itโs important for the future of data privacy! AMA
Once the tools are written, you should be able to take a program written in some language foo and transpile it to a FHE version of foo. See Google's C++ to FHE-C++ transpiler. Thus, you can test/debug your application without FHE before transpiling to something that is FHE.
- Google releases C++ Transpiler for Fully Homomorphic Encryption
- Fully Homomorphic Encryption by Google
- Fully homomorphic encryption (Google GitHub)
- r/crypto - Fully Homomorphic Encryption by Google
- Fully Homomorphic Encryption (FHE)
SEAL
- On Intel SGX, is it possible to set an executable running such that you, the operator, cannot decrypt its state?
-
Haveibeenpwnd
the protocol implementation built on the opensource SEAL library
-
Fully Homomorphic Encryption by Google
FHE has been around for a while now, IBM: https://github.com/homenc/HElib and Microsoft: https://www.microsoft.com/en-us/research/project/microsoft-seal/ both have their own (much more mature) FHE implementations.
-
Fully Homomorphic Encryption (FHE)
It's really great to see more big companies getting into this game, ease of adoption is really the key here.
When it comes to FHE, there are 3 underlying paradigms you can target with compilers:
1. boolean circuits, where you represent your program as encrypted boolean gates. The advantage is that it's as generic as it gets, the drawback is that it's very slow. TFHE is great for that, and it's what is shown here.
2. arithmetic circuits, where you represent your program as a combination of encrypted additions and multiplications. This goes really fast, but you are quickly limited in terms of usecases because you can only do a certain number of arithmetic operations. CKKS/SEAL targets that: https://www.microsoft.com/en-us/research/project/microsoft-s...
3. functional circuits, where you represent your program as a combination of homomorphic functions. Advantage is that you can do very complex things like deep neural network, the drawback being that you have limitations of the bits of precision for the computations. Concrete targets that: https://zama.ai/concrete/
- Microsoft Seal: Fast and Easy-to-Use Homomorphic Encryption Library
-
Would you pay for querying a postgresql database in such a way the server never learned what row you queried for?
Case 2: the encrypted case. You would be encrypting the data itself, so each cell in your database would be encrypted, the filesystem, the tables, the database, and every other aspect of postgresql is left exactly the same. As a matter of fact, you would install this the same way you would install every other postgresql extension. Just run "make install". The only dependency is Microsoft SEAL(https://github.com/microsoft/SEAL) which is open source and you download it and install it from source as well. That is it.
What are some alternatives?
differential-privacy - Google's differential privacy libraries.
HElib - 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.
i2pd - ๐ก I2P: End-to-End encrypted and anonymous Internet
EVA - Compiler for the SEAL homomorphic encryption library
monero - Monero: the secure, private, untraceable cryptocurrency
brainfreeze - Fully Homomorphic Brainfuck
MuchPIR - Homomorphic Encryption PIR Postgres C/C++ Agregate Extension.
Free-the-World-Algorithm - an algorithm to conduct anonymous votes/ polls/ elections/ opinion studies with billions of authenticated voters securely and verifiable
libaco - A blazing fast and lightweight C asymmetric coroutine library ๐ โ ๐โ ๐