liboqs
OpenSSL
liboqs | OpenSSL | |
---|---|---|
11 | 150 | |
1,616 | 24,186 | |
2.0% | 0.8% | |
8.9 | 9.9 | |
6 days ago | 6 days ago | |
C | C | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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
OpenSSL
-
RVM Ruby 2.6.0 — built with custom openssl version on Ubuntu 22.04
ENV OPENSSL_PREFIX=/opt/openssl ENV SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt WORKDIR /tmp RUN git clone --branch OpenSSL_1_0_2n https://github.com/openssl/openssl.git RUN cd openssl RUN ./config shared --prefix=$OPENSSL_PREFIX --openssldir=$OPENSSL_PREFIX/ssl RUN make RUN make install RUN rvm install 2.6.0 -C --with-openssl-dir=$OPENSSL_PREFIX ENV PATH /usr/local/rvm/bin:$PATH RUN rvm --default use ruby-2.6.0 ENV PATH /usr/local/rvm/bin:/usr/local/rvm/rubies/ruby-2.6.0/bin:$PATH ENV GEM_HOME /usr/local/rvm/rubies/ruby-2.6.0/lib/ruby/gems/2.6.0
-
Heartbleed and XZ Backdoor Learnings: Open Source Infrastructure Can Be Improved Efficiently With Moderate Funding
Today, April 7th, 2024, marks the 10-year anniversary since CVE-2014-0160 was published. This security vulnerability known as "Heartbleed" was a flaw in the OpenSSL cryptography software, the most popular option to implement Transport Layer Security (TLS). In more layman's terms, if you type https:// in your browser address bar, chances are high that you are interacting with OpenSSL.
-
Ask HN: How does the xz backdoor replace RSA_public_decrypt?
At this point I pretty much understand the entire process on how the xz backdoor came to be: its execution stages, extraction from binary "test" files etc. But one thing puzzles me: how can the ifunc mechanism be used to replace something like RSA_public_decrypt? Granted this probably stems from my lack of understanding of ifunc, but I was under the impression that in order for the ifunc mechanism to work in your code, you have to explicitly mark specific function with multiple implementations with __attribute__ ((ifunc ("the_resolver_function"))). Looking at the source code of the RSA function in question, ifunc attribute isn't present:
https://github.com/openssl/openssl/blob/master/crypto/rsa/rsa_crpt.c#L51
So how does the backdoor actually replace the call? Does this means that the ifunc mechanism can be used to override pretty much anything on the system?
-
Use of HTTPS Resource Records
OpenSSL and Go crypt/tls has no support yet, so none of the webservers that depend on them support it. Apache, Nginx, and Caddy, they all need upstream ECH support first.
- https://github.com/openssl/openssl/issues/7482
- https://github.com/openssl/openssl/pull/22938
- https://github.com/golang/go/issues/63369
- openssl-3.2.0 released
- Large performance degradation in OpenSSL 3
- OpenSSL 3.2 Alpha 2
-
Encrypted Client Hello – the last puzzle piece to privacy
If I'm understanding the draft correctly, I think the webserver you're hosting your sites on would need it implemented as it requires private keys and ECH configuration. In the example of nginx since it uses openssl, openssl would need to implement it. I found an issue on their Github but it's still open: https://github.com/openssl/openssl/issues/7482
- eBPF Practical Tutorial: Capturing SSL/TLS Plain Text Data Using uprobe
-
OpenSSL Versions... whats the plan here
I confirmed that the systm was on 1.1.1f with openssl version command. Hmm...... I check the openssl version in the repo with apt list... LOL package names wernt helpful. finally went to the repo pages and found that its still on 1.1.1f, https://launchpad.net/ubuntu/+source/openssl. Meenwhile I looked up the version history on https://www.openssl.org/ and saw that 1.1.1v was released at the beginning of this month... ok. I can understand it it was out less then 30 days. I looked up when f came out, end of MARCH 2020. NEARLY 3-1/2 YEARS
What are some alternatives?
codeql - CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
GnuTLS - GnuTLS
libsodium - A modern, portable, easy to use crypto library.
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
kybertest - CLI to encrypt files using quantum-resistant cryptography
LibreSSL - LibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to [email protected] are welcome.
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit