CryptoSwift is a growing collection of standard and secure cryptographic algorithms implemented in Swift
-
Updated
Jul 17, 2021 - Swift
{{ message }}
CryptoSwift is a growing collection of standard and secure cryptographic algorithms implemented in Swift
A shared preference implementation for confidential data in Android. Per default uses AES-GCM, BCrypt and HKDF as cryptographic primitives. Uses the concept of device fingerprinting combined with optional user provided passwords and strong password hashes.
A modern and easy-to-use cryptographic library for .NET Core based on libsodium
A collection of common (interesting) cryptographic mistakes and learning resources.
Nonce-Disrespecting Adversaries: Practical Forgery Attacks on GCM in TLS
Need to encrypt a file before sending it to someone? This is it.
Golang symmetric encryption library
Hoard is a stateless, deterministically encrypted, content-addressed object store.
Minimal AES-128 encryption. Suitable for small embedded systems. Including an on-the-fly key schedule variant for minimal RAM usage.
A lightweight, encrypted, WAN oriented, software defined network device.
A library that provides an encrypted version of the Android shared preferences.
(DEPRECATED - USE: https://developer.apple.com/documentation/cryptokit/aes/gcm) Galois/Counter Mode (GCM) with Advanced Encryption System (AES).
VESvault End-to-End Encryption API: Encrypt Everything Without Fear of Losing the Key
CLI for Shamir's Secret Sharing and AES key generation, encryption, and decryption.
macOS (incl big sur) call history decryptor/converter to CSV format.
ECIES on Twisted Edwards Curve25519 using AES-GCM and HKDF-SHA256
File encryption for multiple participants
zenroomjs
Add a description, image, and links to the aes-gcm topic page so that developers can more easily learn about it.
To associate your repository with the aes-gcm topic, visit your repo's landing page and select "manage topics."
First of all, thanks for this great tutorial! I learned a lot following along!
After going through the code several times, I'm wondering why we would need to explicitly encrypt/decrypt field values of our custom
EncryptedFieldtype before saving them in the database. Isn't that why we define our custom Ecto Types to begin with, so that we don't need to encrypt/decrypt values manually and expl