I'm sure we COULD use it. But really its a preference thing. I want to use the SCRYPT hashing alorithm. And I want AES-256 GCM. Why not just use them directly from a trusted source?
I like scrypt for our use case because we are simply trying to make it hard to brute force access. Scrypt requires high powered computation AND memory in order to continue guessing keys.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Node's crypto library
I'd avoid it. It seems really low level from reading some of your source code. Check out a Libsodium port for Node.js.
Using low-level cryptography libraries make it easy to screw up.
Hmm? It's just hashing and ciphering. Adding an extra dependency in the middle for no reason is scarier to me.
Libsodium is a cryptography library that's easy to use. You should be using that instead of what you're doing.
I disagree. I understand what I'm doing, I'm well enough versed in cryptography to prefer the actual crypto library than training wheels.
Libsodium isn't "training wheels". It's a production ready solution that most people should be using.
I'm sure we COULD use it. But really its a preference thing. I want to use the SCRYPT hashing alorithm. And I want AES-256 GCM. Why not just use them directly from a trusted source?
Okay. It makes sense. Why do you want AES-256 in GCM mode? And why Scrypt?
From a high level GCM is considered more secure than CBC. Especially at lower resolutions. Good link: crypto.stackexchange.com/questions...
I like scrypt for our use case because we are simply trying to make it hard to brute force access. Scrypt requires high powered computation AND memory in order to continue guessing keys.