C Encryption

Open-source C projects categorized as Encryption

Top 23 C Encryption Projects

  • OpenSSL

    TLS/SSL and crypto library

    Project mention: Heartbleed and XZ Backdoor Learnings: Open Source Infrastructure Can Be Improved Efficiently With Moderate Funding | dev.to | 2024-04-07

    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.

  • VeraCrypt

    Disk encryption with strong security based on TrueCrypt

    Project mention: VeraCrypt: Free, open source, disk encryption for Windows, Mac OS X, Linux | news.ycombinator.com | 2023-10-01

    [1] - https://github.com/veracrypt/VeraCrypt

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  • GmSSL

    支持国密SM2/SM3/SM4/SM9/SSL的密码工具箱

  • s2n

    An implementation of the TLS/SSL protocols

    Project mention: S2n-TLS – A C99 implementation of the TLS/SSL protocol | /r/programming | 2023-12-05
  • wolfssl

    The wolfSSL library is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3!

  • c-toxcore

    The future of online communications.

    Project mention: Tox Core is one of the nicest-to-read C codebases | news.ycombinator.com | 2024-03-22
  • magma

    The magma server daemon, is an encrypted email system with support for SMTP, POP, IMAP, HTTP and MOLTEN,. Additional support for DMTP and DMAP is currently in active development. (by lavabit)

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  • Themis

    Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.

  • 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.

  • Minizip-ng

    Fork of the popular zip manipulation library found in the zlib distribution.

  • enchive

    Encrypted personal archives

  • Cronos

    PoC for a sleep obfuscation technique leveraging waitable timers to evade memory scanners. (by Idov31)

  • pgsodium

    Modern cryptography for PostgreSQL using libsodium.

    Project mention: Macaroons Escalated Quickly | news.ycombinator.com | 2024-01-31

    I like the "solve the now" perspective here, and having code examples is very helpful to understand some of the rational behind the approach. Having read your previous "tedious survey"[0] post on various token formats, I generally agree with a lot of your conclusions. Curious though about your thought process wrt macaroons vs biscuits.

    To me the one major downside of macaroons has always been the single shared root symmetric key. Many use cases are addressed by third party attenuation, but then there are the problems like key rotation, having to do online verification, no built in encryption, no peer-to-peer support through an "untrusted" fly.io, and no third party token verification without decryption like in signcryption[1] schemes. Of course this is traded off by having to do PK issuance and management so I can see the simplicity of it.

    Is fly.io scoping this pretty hard to just auth tokens with third party attenuation, or do you see further development and maybe moving to other token systems like biscuit when/if the need arises to address those known issues?

    fwiw I've done a bit of research work myself on a token format using signcryption [2] where I explored addressing some of these ideas (but not the attenuation side of it yet, which I get is a big deal here).

    [0] https://fly.io/blog/api-tokens-a-tedious-survey/

    [1] https://github.com/jedisct1/libsodium-signcryption

    [2] https://github.com/michelp/pgsodium/blob/feat/signcryption-t...

  • libdime

    The DIME resolver library and command line utilities.

  • sqleet

    SQLite3 encryption that sucks less

  • lurch

    XEP-0384: OMEMO Encryption for libpurple.

  • VeraCrypt-DCS

    VeraCrypt EFI Bootloader for EFI Windows system encryption (LGPL)

  • mkinitcpio-ykfde

    Full disk encryption with Yubikey (Yubico key)

  • CatCrypto

    An easy way for hashing and encryption.

  • disco-c

    A tiny C cryptographic library to encrypt sessions, authenticate messages, sign, hash, etc. based only on SHA-3 and Curve25519

  • libsodium-signcryption

    Signcryption using libsodium.

    Project mention: Macaroons Escalated Quickly | news.ycombinator.com | 2024-01-31

    I like the "solve the now" perspective here, and having code examples is very helpful to understand some of the rational behind the approach. Having read your previous "tedious survey"[0] post on various token formats, I generally agree with a lot of your conclusions. Curious though about your thought process wrt macaroons vs biscuits.

    To me the one major downside of macaroons has always been the single shared root symmetric key. Many use cases are addressed by third party attenuation, but then there are the problems like key rotation, having to do online verification, no built in encryption, no peer-to-peer support through an "untrusted" fly.io, and no third party token verification without decryption like in signcryption[1] schemes. Of course this is traded off by having to do PK issuance and management so I can see the simplicity of it.

    Is fly.io scoping this pretty hard to just auth tokens with third party attenuation, or do you see further development and maybe moving to other token systems like biscuit when/if the need arises to address those known issues?

    fwiw I've done a bit of research work myself on a token format using signcryption [2] where I explored addressing some of these ideas (but not the attenuation side of it yet, which I get is a big deal here).

    [0] https://fly.io/blog/api-tokens-a-tedious-survey/

    [1] https://github.com/jedisct1/libsodium-signcryption

    [2] https://github.com/michelp/pgsodium/blob/feat/signcryption-t...

  • libcrux

    The formally verified crypto library for Rust

    Project mention: Verified ML-KEM (Kyber) in Rust | news.ycombinator.com | 2024-02-01
  • rvault

    rvault: secure and authenticated store for secrets and small documents

  • SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020). The latest post mention was on 2024-04-07.

C Encryption related posts

Index

What are some of the best open-source Encryption projects in C? This list will help you:

Project Stars
1 OpenSSL 24,090
2 VeraCrypt 6,169
3 GmSSL 4,694
4 s2n 4,446
5 wolfssl 2,166
6 c-toxcore 2,156
7 magma 1,820
8 Themis 1,807
9 LibTomCrypt 1,477
10 Minizip-ng 1,152
11 enchive 615
12 Cronos 532
13 pgsodium 508
14 libdime 416
15 sqleet 371
16 lurch 279
17 VeraCrypt-DCS 126
18 mkinitcpio-ykfde 105
19 CatCrypto 68
20 disco-c 62
21 libsodium-signcryption 57
22 libcrux 38
23 rvault 33
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com