Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Liboqs Alternatives
Similar projects and alternatives to liboqs
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
codeql
CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cjdns
An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
liboqs reviews and mentions
-
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:
-
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
-
A note from our sponsor - InfluxDB
www.influxdata.com | 19 Apr 2024
Stats
open-quantum-safe/liboqs is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of liboqs is C.