C2SP
constant-time
C2SP | constant-time | |
---|---|---|
15 | 4 | |
236 | 18 | |
8.1% | - | |
7.4 | 0.0 | |
about 1 month ago | about 2 years ago | |
Python | WebAssembly | |
GNU General Public License v3.0 or later | 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.
C2SP
- Sunlight, a Certificate Transparency log implementation
-
Do any libraries exist for zero-trust file storage (storing client-encrypted data on the server without the key)?
Age is a modern, respected crypto solution: https://github.com/C2SP/C2SP/blob/main/age.md
-
argon2 vs bcrypt vs scrypt vs pbkdf2
Argon2 is the best choice, but scrypt may be more easily available: https://github.com/C2SP/C2SP/issues/10
-
Age: Modern file encryption format with multiple pluggable recipients
Hi! I read and appreciated your issues and discussions, sorry I didn't get to respond to them yet, but I've been thinking about it.
Although I don't disagree that parsing text is hard, I also think that parsing variable-size binary formats is hard (and there is a tall, tall pile of bugs to confirm that). Really, parsing is hard. Rather than count on one design or the other to be bug-proof, I worked on a large test suite to help implementations catch their parsing bugs. [https://c2sp.org/CCTV/age] I think it would have found one of the issues you reported if that implementation had integrated it, and I am going to add vectors for various resource exhaustion scenarios which I hope would have found the other. (I am not going to look at what it is exactly, so I will know if I made the suite comprehensive enough without being too specific about this bug.)
I also liked your observation that it would have been nice if the header was streamable. [https://github.com/C2SP/C2SP/issues/28] It went on the pile labeled "regrets / for v2 when it comes", thank you.
-
age.el: age encryption support for Emacs
I think it's ironic that you imply a "dozen of immature crypto libraries" are used in the Age spec. It's quite the opposite and the Age spec provides a reduction in so-called "yolo crypto" versus the OpenPGP spec. See: https://github.com/C2SP/C2SP/blob/main/age.md and also give https://latacora.micro.blog/2019/07/16/the-pgp-problem.html# for a pretty accurate overview of what's wrong with OpenPGP.
-
Pa – a simple password manager based on age
… okay, then look at the spec, which is beautifully simple: https://github.com/C2SP/C2SP/blob/main/age.md#the-scrypt-rec...
- The recent security issues with LastPass made me wonder - couldn't I just use an encrypted notepad app on my phone to achieve the same level of security?
-
Age WASM - age encryption tool in the browser
I had the same question. I believe it refers to “Actually Good Encryption” (https://github.com/C2SP/C2SP/blob/main/age.md).
constant-time
-
A beginner's guide to constant-time cryptography (2017)
I noticed in July of 2022 that Go did exactly the vulnerable example and reported it to the security team.
https://github.com/golang/go/issues/53849
It was fixed as of Go 1.21 https://go.dev/doc/go1.21
---
The article cites JavaScript, which is not constant time. There's no sure way to do constant time operations in JavaScript and thus no secure way to do crypto directly in Javascript. Browsers like Firefox depend on low level calls which should be implemented in languages that are constant time capable.
JavaScript needs something like constant time WASM in order to do crypto securely, but seeing the only constant time WASM project on GitHub has only 16 stars and the last commit was 2 years ago, it doesn't appear to have much interest. https://github.com/WebAssembly/constant-time
However, for JavaScript, I recommend Paul's library Noble which is "hardened to be algorithmically constant time". It is by far the best library available for JavaScript. https://github.com/paulmillr/noble-secp256k1
-
Age WASM - age encryption tool in the browser
Also see the constant time spec: https://github.com/WebAssembly/constant-time
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
I'm waiting for constant time WASM. https://github.com/WebAssembly/constant-time/blob/main/propo...
-
Ed25519 Online Tool - Sign, Verify, and Generate Ed25519 Keys.
Also: We're excited for constant time Wasm.
What are some alternatives?
sops - Simple and flexible tool for managing secrets
Ed25519Tool - Ed25519 signing and verification online tool.
age.el - Transparent age encryption support for Emacs modeled after EPG/EPA
proposal-ptc-syntax - Discussion and specification for an explicit syntactic opt-in for Tail Calls.
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
pa - a simple password manager. encryption via age, written in portable posix shell
spec - WebAssembly specification, reference interpreter, and test suite.
rage - A simple, secure and modern file encryption tool (and Rust library) with small explicit keys, no config options, and UNIX-style composability.
ecma262 - Status, process, and documents for ECMA-262
passage - A fork of password-store (https://www.passwordstore.org) that uses age (https://age-encryption.org) as backend.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.