[Isaac Schlueter <[email protected]> (2013-02-01 16:45:25 UTC)]
> The binary encoding is probably not ever going away. It may be
> deprecated, but people use it, and meh. It's not hurting anybody.
Good to know. I'll try to avoid it when possible, though. (Though I
suppose it might as well have been called the latin-1 encoding. I have
lived for years with latin-1 waiting for the world to support unicode.
We're almost there, but latin-1 encoded stuff is still everywhere.)
> The crypto API will return a buffer by default in 0.10. If you would
> like to get a binary encoded string, you can add this to your code now
> to future-proof it:
>
> crypto.pbkdf2(..., function(er, derivedKey) {
> if (typeof derivedKey === 'string') {
> derivedKey = new Buffer(derivedKey, 'binary');
> }
> [...]
*smacks forehead* Of course, should have thought of that, future
proofing not only the user database, but the code as well. Thanks.
- Harald
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
