liboqs
libsodium
liboqs | libsodium | |
---|---|---|
11 | 30 | |
1,616 | 11,927 | |
2.0% | - | |
8.9 | 8.7 | |
6 days ago | 6 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
liboqs
-
Show HN: filippo.io/mlkem768 – Post-Quantum Cryptography for the Go Ecosystem
How about liboqs from OpenQuantumSafe? It includes an implementation of most PQC primitives proposed to date:
https://github.com/open-quantum-safe/liboqs
-
2048 Bit RSA and the Year 2030
Part of the issue as a prospective cryptographic user/consumer is that not only do I not know which algorithm(s) should be used, the most likely library https://github.com/open-quantum-safe/liboqs also explicitly states that it shouldn't be used in production.
Hybrid deployment (E.G. with ECC using a curve like 25519) is a great recommendation and probably obvious, far more so than picking a winner among the available post quantum possibly safe algorithms.
-
Changing default Openssl signature algorithm and key exchange algorithm to use PQC Dilithium and Kyber
Hi everyone! I am currently trying to modify some settings within OpenSSL. My goal is to change the default algorithms that OpenSSL uses for generating certificates and signatures, as well as the key exchange method. Specifically, I want OpenSSL to default to the ones provided by OQS (https://openquantumsafe.org/), Dilithium and Kyber.
-
Ask HN: What's the Status of Post-Quantum (PQC) in TLS and QUIC?
NIST - https://csrc.nist.gov/Projects/post-quantum-cryptography/post-quantum-cryptography-standardization
NSA - https://www.tomshardware.com/news/us-national-security-agency-issues-update-on-crypto-resistant-encryption
ISARA - https://www.isara.com/products/isara-radiate.html
OQS (NIST reports on this) - https://openquantumsafe.org
MSFT - https://www.microsoft.com/en-us/research/project/post-quantum-tls
Wikipedia's take - https://en.wikipedia.org/wiki/Post-quantum_cryptography
- Liboqs - Quantum safe cryptography library (not for production use)
- Liboqs – Quantum safe cryptography research library
-
A plan for cybersecurity and grid safety
Efforts: Open Quantum Safe project
-
What's the strongest encryption available for Python and which library do you use to implement it?
One thing I will mention for "most secure" is that you could add a second layer of encryption based on liboqs which aims to be quantum resistant (mostly important for asymmetric algorithms, symmetric algorithms are already thought to be quantum resistant). We don't know if any of the quantum resistant algorithms are any good or not. They could all be broken, so only use them as a second layer on top of existing encryption schemes, but if you want "the best", then that's what I would do: use standard tools with the biggest variants of the algorithm and then put a layer of post-quantum crypto on top of it.
- Run a static library in C
- Open Quantum Safe – open-source prototyping of quantum-resistant cryptography
libsodium
-
Libsodium: A modern, portable, easy to use crypto library
Libsodium has been around for a while, so probably the reason it was posted is that version 1.0.19 was just released: https://github.com/jedisct1/libsodium/releases/tag/1.0.19-RE...
Updated NuGet and Swift packages are going to be uploaded soon.
AEGIS-128X and 256X are not there yet, but if you need them, they are available in libaegis: https://github.com/jedisct1/libaegis
All the code from libaegis will eventually be merged into libsodium, including the incremental update API which is especially useful for TLS.
- Libsodium 1.0.19 Released
- FLaNK Stack Weekly for 20 June 2023
-
Libsodium Still Relevant and Maintained?
To version the dependency you can check the current stable tree in git and save the date and git hash.
-
I created an encrypted command line jounal
To address both of these vulnerabilities, you should instead use a library that handles these sharp edges for you. A well received library in the security and cryptography communities is libsodium. It has high level functions that handle password hashing and data encryption for you, reducing the risk that you introduce vulnerabilities in your code, such as you have here.
-
Why can't I burn scam tokens by sending them to 0x000000000000000000000000000000000000dEaD?
In general, cryptography is really hard. So for example, an attacker could construct a message that if you signed would leak information, ie it reduces the space of possible keys such that it can be brute forced. I’m not entirely sure if you could do that with a transfer function. But it’s certainly possible. That said, there are a ton of smart devs trying to prevent that as well so I’m not assuming anything here. But prudent practices are likely good to follow. Be very careful calling anything from your cold wallet etc. Use disposable keys for anything a bit risky. I took a sec to google an example and this is the closest I could find. https://github.com/jedisct1/libsodium/issues/170
-
Some questions from a noob Rustacean
Hi everyone! I'm learning Rust while on a break between jobs, and as I'm particularly interested in interfacing Rust with C and in cryptography, I've decided to write a wrapper around libsodium (https://github.com/jedisct1/libsodium) in Rust. This is purely a hobby project and I probably won't ever release it as there are already some open-source Rust bindings available for the library.
-
Librandombytes – a public domain library for generating randomness
Can anyone recommend between Librandombytes and libsodium ramdombytes?
https://github.com/jedisct1/libsodium/tree/master/src/libsod...
What are some alternatives?
OpenSSL - TLS/SSL and crypto library
codeql - CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
Crypto++ - free C++ class library of cryptographic schemes
cjdns - An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.
mbedTLS - An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months between releases.
human_security - simple rsa signing API
libhydrogen - A lightweight, secure, easy-to-use crypto library suitable for constrained environments.
kybertest - CLI to encrypt files using quantum-resistant cryptography
Botan - Cryptography Toolkit
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
Bcrypt - Modern(-ish) password hashing for your software and your servers