nowfound

Alternatives

Products that do what LightPHE: Lightweight Partially Homomorphic Encryption for Python does

Homomorphic encryption enables computations to be performed directly on encrypted data without requiring access to the private key. This allows data to be securely stored in the cloud while still being processed using the cloud’s computational power. Meanwhile, the cloud remains unaware of the actual data it is handling. Although fully homomorphic encryption has become available in recent years, when considering performance trade-offs, partially homomorphic encryption proves to be a more efficient and practical choice. It is significantly faster, requires fewer computational resources, and…

  1. 1DH
  2. 2TF
  3. 3NA
  4. 4PA
  5. 5RV
  6. 6AA
  7. 7LA
  8. 8SK
  9. 9AK
  10. 10LS
  11. 11CA
  12. 12ET
  13. 13HI
  14. 14WM
  15. 15GE
  16. 16NQ

    Hey HN, We're building ncrypt, an open-source encrypted file manager that allows you to store, manage, and privately query your files using fully homomorphic encryption (FHE). This project originally started as a simple SFTP-like CLI for my personal S3 buckets which I used to send and retrieve encrypted files and have more granular control over key rotation. As the number of files that I was storing grew, file discovery started to become a problem, and I found myself frequently having to download and decrypt files to inspect their contents. Rather than leaving them unencrypted in S3 and…

    2025 · github.com

  17. 17SE

    Hello. I made this project as an experiment in using key cryptography for user identity in a client server model, and for some future peer to peer projects that I am working on. I am looking for feedback, please let me know what you think. Also, Merry Christmas to HN! :-)

    2022 · github.com

  18. 18CD
  19. 19AI

    I really couldn't find a simple wrapper to pycrypto that would encrypt data correctly in Python 3. So I tried to follow the instructions at http://www.daemonology.net/blog/2009-06-11-cryptographic-right-answers.html (written by HN's cperciva) and wrote https://github.com/andrewcooke/simple-crypt Is that OK? Given the problems Tarsnap had with CTR mode, was it wrong to follow those instructions anyway? Have I got the offset handling right? It seemed like it would be better to write this once, get it revised here, and then publish it (I'll make an egg for pypi once it seems OK) than quietly…

    2012

  20. 20SA
  21. 21CS

    2016 · github.com

  22. 22DP
  23. 23UD
  24. 24PA

Ranked by how close each launch is in meaning, then by votes. Refine with a description →