liboqs
infer
liboqs | infer | |
---|---|---|
11 | 42 | |
1,616 | 14,708 | |
2.0% | 0.3% | |
8.9 | 9.9 | |
6 days ago | 6 days ago | |
C | OCaml | |
GNU General Public License v3.0 or later | 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.
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
infer
-
An Introduction to Temporal Logic (With Applications to Concurrency Problems)
I think most development occurs on problems that can't be formally modeled anyway. Most developers work on things like, "can you add this feature to the e-commerce site? And can the pop-up be blue?" which isn't really model-able.
But that's not to say that formal methods are useless! We can still prove some interesting aspects of programs -- for example, that every lock that gets acquired later gets released. I think tools like Infer[0] could become common in the coming years.
[0]: https://fbinfer.com/
- Should I Rust or should I Go
-
Enforcing Memory Safety?
Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code.
-
Interesting ocaml mention in buck2 by fb
Meta/Facebook are long time OCaml users, their logo is on the OCaml website. Their static analysis tool and its predecessor are both written in OCaml.
-
CISA Director Easterly's comments about cyber security. Agree or disagree?
Then this idea that the US government will tell tech companies how to write secure software. Let's get this straight, the private sector, especially big tech is miles ahead of US government in this regard. Microsoft literally invented threat modelling and modern exploit mitigations. Facebook has the best appsec processes pretty much in the whole world, including their own cutting edge code analyzer. AWS uses formal verification everywhere. Meanwhile the US government itself runs mission-critical systems that's almost literally held together by bubble gum and toothpicks. Maybe they could dial down the arrogance a tad, get their own shit together, learn how this cyber stuff is actually done and only then try lecturing everyone else.
-
A plan for cybersecurity and grid safety
Efforts: Dependabot, CodeQL, Coverity, facebook's Infer tool, etc
-
A quick look at free C++ static analysis tools
I notice there isn't fbinfer. It's pretty cool, and is used for this library.
-
silly guy
"Move fast, break stuff" is a great approach when you aren't pushing the broken bits to production. Fuck, even Facebook, the big "move fast, break stuff" company, uses tools to detect errors in its continuous integration toolchain. https://fbinfer.com/
- OCaml 5.0 Multicore is out
-
Beyond Functional Programming: The Verse Programming Language (Epic Games' new language with Simon Peyton Jones)
TBH, there's a non-zero amount of non-"ivory tower" tools you may have used that are written in functional languages. Say, Pandoc or Shellcheck are written in Haskell; Infer and Flow are written in OCaml. RabbitMQ and Whatsapp are implemented in Erlang (FB Messenger was too, originally; they switched to the C++ servers later). Twitter backend is (or was, at least) written in Scala.
What are some alternatives?
OpenSSL - TLS/SSL and crypto library
SonarQube - Continuous Inspection
codeql - CodeQL: the libraries and queries that power security researchers around the world, as well as code scanning in GitHub Advanced Security
Spotbugs - SpotBugs is FindBugs' successor. A tool for static analysis to look for bugs in Java code.
libsodium - A modern, portable, easy to use crypto library.
Error Prone - Catch common Java mistakes as compile-time errors
cjdns - An encrypted IPv6 network using public-key cryptography for address allocation and a distributed hash table for routing.
FindBugs - The new home of the FindBugs project
human_security - simple rsa signing API
PMD - An extensible multilanguage static code analyzer.
kybertest - CLI to encrypt files using quantum-resistant cryptography
Checkstyle - Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. By default it supports the Google Java Style Guide and Sun Code Conventions, but is highly configurable. It can be invoked with an ANT task and a command line program.