STM32-Bootloader
libsodium
STM32-Bootloader | libsodium | |
---|---|---|
2 | 30 | |
224 | 11,927 | |
- | - | |
0.0 | 8.7 | |
almost 3 years ago | 6 days ago | |
C | C | |
Apache License 2.0 | 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.
STM32-Bootloader
-
Easiest way to firmware update
Hi all! So I'm looking for the easiest and fastest way to create a firmware update desktop app for an STM32 device (Arm Cortex M7). I would like to have something like CubeProgrammer, but way less functionalities (just programming/flashing). Being a commerciall product for non-programmers CubeProgrammer is not fine. I want something proprietary with my GUI. So, .... the strategy I found online is to create a custom bootloader (like this: https://github.com/viktorvano/STM32-Bootloader) and control it with a Java app with serial communication libraries. But why do you NEED a custom bootlader? Can't I just flash to the flash memory (from 0x8000000) and let the default bootloader take care of things? Easier and less flash memory usage. Security is not the priority. Ease and fast implementation is the priority.
-
When you only know how to write brute force algorithms.
You're writing the first stage of a bootloader for a chip your company makes, and your SDK will provide the users with this code. EG this file from ST's CubeMX picked out of the first project containing it I found on GitHub.
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?
BLAKE3 - the official Rust and C implementations of the BLAKE3 cryptographic hash function
OpenSSL - TLS/SSL and crypto 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.
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
LibTomCrypt - LibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines.
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.
Tiny AES128 in C - Small portable AES128/192/256 in C
Tink - Tink is a multi-language, cross-platform, open source library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse.