libsodium
cryptography
Our great sponsors
libsodium | cryptography | |
---|---|---|
30 | 70 | |
11,852 | 6,226 | |
- | 2.5% | |
8.7 | 9.9 | |
25 days ago | about 21 hours ago | |
C | Python | |
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.
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.
- FLaNK Stack Weekly for 20 June 2023
-
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.
-
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...
-
Initial impact report about this week's EdDSA Double-PubKey Oracle attack in 40 affected crypto libs
Feature request submitted to libsodium: https://github.com/jedisct1/libsodium/issues/1191
-
Dangerous toys: Anything to ed25519 (SSH Keys)
This article [0] has a good explanation of why clamping is necessary. But the process is very simple, you just generate 256 random bits, clear the three lowest order to avoid small subgroup attacks, then clear the highest order and set the second highest order to avoid side-channel attacks which may occur if an implementation isn’t constant-time. The Libsodium source shows this pretty clearly: [1], lines 18-23.
0: https://www.jcraige.com/an-explainer-on-ed25519-clamping
1: https://github.com/jedisct1/libsodium/blob/master/src/libsod...
- Information and learning resources for cryptography newcomers
-
monero-python 0.99 is released, testers welcome!
Finally I managed to replace the slow pure-Python reference implementation of Ed25519 cryptography with pynacl which is a binding to libsodium, the industry standard lightning-fast C library.
cryptography
-
We build X.509 chains so you don't have to
Congratulations to the authors, this was a feature that was dearly missing from pyca/cryptography. It took a long time to get right.
For the history: https://github.com/pyca/cryptography/issues/2381
-
“Our paying customers need X, when will you fix it?”
Some context:
- The cryptography dependency used by the current release of mitmproxy has a CVE related to an OpenSSL vulnerability (https://github.com/pyca/cryptography/security/advisories/GHS...)
- The main branch of mitmproxy has already upgraded to the latest version of the cryptography package
- The author of the package does not believe the CVE impacts users of mitmproxy so a release including this commit has not been made
-
Microservice memory profiling
first, I did see a correlation between an endpoint being heavily hit in a given time window, and an increase of memory usage that didn't went down afterwards. The endpoint didn't do much so I went through every instruction - is a global variable appended indefinitely ? Is a cache decorator growing without a limit set ? Do I use a 3rd party that has a known issue ? Turns out, it was using cryptography, so I looked up known issues. Saw an issue about a leak when using load_pem_x509_certificate https://github.com/pyca/cryptography/issues/4833 - which I used ! I could fortunately just upgrade the library
-
I love building a startup in Rust. I wouldn't pick it again
> A big problem with Rust, long-term, is that the kind of programs that really need it are somewhat out of today's mainstream. It's not that useful for webcrap. It's not that useful for phone apps. The AI people use Jupyter notebooks and Python to drive code on GPUs.
One thing this is missing is that Rust is useful for libraries callable by many different languages. You may or may not want to use it to build an actual Web app (I personally think it's a solid choice, but reasonable people can disagree). But for building, say, the Python cryptography library [1], which is used as a part of "webcrap" and Jupyter notebooks, Rust is clearly an excellent option. Nobody is going to build core Python infrastructure in Go or Node, and there will always be a need for plumbing libraries.
-
Azure CTO: “It's time to halt starting any new projects in C/C++ ”
> I am curious. Could you give some more context?
Probably talking about this: https://github.com/pyca/cryptography/issues/5771
- Zig, the Small Language
-
Using a src directory for a Python package
As for an example, cryptography is the general example I recommend here: https://github.com/pyca/cryptography
-
Difference between ruby 2 and ruby 3?
Wasn't entirely serious, just this crap https://github.com/pyca/cryptography/issues/5771
-
OpenSSL Security Advisory [5 July 2022]
The modes of operation aren't the main reason people use OpenSSL; it's the support for all the gnarly (and less gnarly) protocols and wire formats that show up when doing applied cryptography.
Progress is being made on replacing OpenSSL in a lot of contexts (specifically, the RustCrypto[1] folks are doing excellent work and so is cryptography[2]), but there are still plenty of areas where OpenSSL is needed to compose the mostly algebraic cryptography with the right wire format.
-
Help with basic steps in an application design
2) Which cryptographic library would be recommended for this purpose? I've seen people using PyCrypto (https://github.com/pycrypto/pycrypto) which seems simple enough, but that one seems not maintained anymore. I've also seen keyring.cryptfile (https://github.com/frispete/keyrings.cryptfile) and pyca/cryptography (https://github.com/pyca/cryptography) but I'm not really sure if any of those should actually be used for my purpose?
What are some alternatives?
PyCrypto - The Python Cryptography Toolkit
OpenSSL - TLS/SSL and crypto library
pycryptodome - A self-contained cryptographic library for Python
pyOpenSSL -- A Python wrapper around the OpenSSL library - A Python wrapper around the OpenSSL library
PyNacl - Python binding to the Networking and Cryptography (NaCl) library
Paramiko - The leading native Python SSHv2 protocol library.
Crypto++ - free C++ class library of cryptographic schemes
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.
Passlib
libhydrogen - A lightweight, secure, easy-to-use crypto library suitable for constrained environments.
Botan - Cryptography Toolkit
Bcrypt - Modern(-ish) password hashing for your software and your servers