azure-iot-sdk-c
s2n
azure-iot-sdk-c | s2n | |
---|---|---|
3 | 9 | |
573 | 4,449 | |
0.2% | 0.2% | |
8.2 | 9.5 | |
2 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.
azure-iot-sdk-c
-
I'm trying to communicate with the iot hub via an edge gateway device
I'm trying to send data via an edge gateway device. I have set up my edge device which is a linux machine (https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-devices-at-scale-linux-symmetric?view=iotedge-1.4&tabs=individual-enrollment%2Cubuntu), now I need to send data from an esp32 device to the iot hub via the edge gateway device. The example code given in the azure iot edge documentation is in C (https://github.com/Azure/azure-iot-sdk-c/blob/main/iothub_client/samples/iotedge_downstream_device_sample/iotedge_downstream_device_sample.c), I need it in the arduino framework for my esp32 device.
-
Cannot connect Arduino MKR 1010 WiFi to Azure IoT Hub via X509 CA Signed certificate
Create CA signed certificate, using ECC algorithm for signing, following this guide - https://github.com/Azure/azure-iot-sdk-c/blob/main/tools/CACertificates/CACertificateOverview.md
-
What projects, products do you like or have tried when connecting embedded devices to the cloud?
Another route is the SDKs provided by the cloud vendors (for example, the Azure c sdk). All of the big ones have it.
s2n
-
S2n-TLS – A C99 implementation of the TLS/SSL protocol
It seems to support multiple options but requires you pick at least one of them. https://github.com/aws/s2n-tls/blob/main/docs/BUILD.md#build...
-
OpenSSL 1.1.1 End of Life
I think GnuTLS is probably the second most popular TLS library, after openssl.
I'll also mentions s2n and rustls-ffi for completeness as C libraries, though the former isn't widely used, and the latter is very experimental still. https://github.com/aws/s2n-tls and https://github.com/rustls/rustls-ffi respectively.
-
I want XAES-256-GCM/11
I've seen operating on unauthenticated plaintext enough times to list it as my own pet peeve with AES-GCM. But it's a problem for chunked messages too. A few years ago we released a SCRAM mode that makes very minimal changes to AES-GCM so that it mathematically can't operate on unauthenticated plaintext. https://github.com/aws/s2n-tls/tree/main/scram
-
Golang is evil on shitty networks
> The documentation is kind of vague, but apparently you have to re-enable it regularly.[3]
This is correct. And in the end it means more or less that setting the socket option is more of a way of sending an explicit ACK from userspace than a real setting.
It's not great for common use-cases, because making userspace care about ACKs will obviously degrade efficiency (more syscalls).
However it can make sense for some use-cases. E.g. I saw the s2n TLS library using QUICKACK to avoid the TLS handshake being stuck [1]. Maybe also worthwhile to be set in some specific RPC scenarios where the server might not immediately send a response on receiving the request, and where the client could send additional frames (e.g. gRPC client side streaming, or in pipelined HTTP requests if the server would really process those in parallel and not just let them sit in socket buffers).
[1] https://github.com/aws/s2n-tls/blob/46c47a71e637cabc312ce843...
-
S2n-QUIC (Rust implementation of QUIC)
It looks like by default s2n-quic uses this TLS implementation, which is not based on the ring crate (though it is written in C)
https://github.com/aws/s2n-tls
-
LibreSSL Languishes on Linux
I would be interested in the other SSL implementations:
- https://github.com/awslabs/s2n
- https://boringssl.googlesource.com/boringssl
- https://bearssl.org/
Are these subpar implementations or there are other reasons not to use these?
What are some alternatives?
cgltf - :diamond_shape_with_a_dot_inside: Single-file glTF 2.0 loader and writer written in C99
OpenSSL - TLS/SSL and crypto library
azure-iot-sdk-python - A Python SDK for connecting devices to Microsoft Azure IoT services
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.
pico-servo - A simple C library for controlling servos using a Raspberry Pi Pico
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.
sod - An Embedded Computer Vision & Machine Learning Library (CPU Optimized & IoT Capable)
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.
couchbase-rs - The official, community supported Couchbase Rust SDK
libsodium - A modern, portable, easy to use crypto library.
Digital-Twins-Azure-IoT-Hub - Python scripts used for my Master Thesis related to the Digital Twins in the IoT platform
Botan - Cryptography Toolkit