google/tink is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Similar projects and alternatives to Tink based on common topics and language
Open source code for basic Boxcryptor file decryption
Multi-platform transparent client-side encryption of your files in the cloud
Scout APM - Leading-edge performance monitoring starting at $39/month. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
Welcome to the AWS Code Examples Repository. This repo contains code examples used in the AWS documentation, AWS SDK Developer Guides, and more. For more information, see the Readme.rst file below.
Bouncy Castle Java Distribution (Mirror)
JCrypTool Core Plug-ins (by jcryptool)
JCrypTool Crypto Plug-ins (by jcryptool)
GraalVM: Run Programs Faster Anywhere :rocket:
Storing Sensitive Information in Django
reddit.com/r/django | 2021-03-14
Building a Secure Signed JWT
reddit.com/r/programming | 2021-01-15
appears to be focused on cryptography and not token signing. Maybe more of a complement? I did see a section about digital signing: https://github.com/google/tink/blob/master/docs/PRIMITIVES.md#digital-signatures and don't see any reason you couldn't integrate tink to sign JWTs.
Independent Audit: Insights into the Source Code of Boxcryptor
news.ycombinator.com | 2021-01-07
4. Output AES-CBC-DECRYPT(KE, IV, C) with PKCS#5 padding.
The core of the problem is that, while they use the HMAC to check that the ciphertext is authentic (which is a bit odd, given that they seem to claim that authenticity shouldn't matter), they never check that the IV is authentic (it's never computed in the HMAC).
The way that AES-CBC decryption works, for first 16-bytes of the decryption is AES-BLOCK-DECRYPT(KE, first 16 bytes of C) XOR IV. As a result, if the IV isn't authenticated (which it's not), then any bit that the attacker flips in the IV will flip the corresponding bit in the ciphertext. Because PKCS#5 padding is used, given a padding oracle, an adversary could decrypt messages under 16 bytes in length.
The moral of the story is DO NOT ROLL YOUR OWN CRYPTO! Rolling your own crypto can be fun and educational and informative, but DON'T DEPLOY IT!