crypto: add sync methods, deprecate optional callbacks

[jonathanong]

See #5

• would you like me to add/change tests?
• didn't bother disallowing callbacks in the sync version. after all this is about the public API. is that something you guys want?
• want doc updates?
• only changed .randomBytes() and .pseudoRandomBytes(). were there others?

[piscisaureus]

I like this. @iojs/tc

[trevnorris]

+1

[ruimarinho]

Someone mentioned on another issue (I can't find right now) that we should consider aligning our crypto API with the WebCryptoAPI, specifically using getRandomValues. I think it was an excellent idea. Would this be the moment to consider it?

[trevnorris]

@ruimarinho Since 1.0.0-alpha is pushing for release, not right now. Though if there's not an official issue open asking for it then the issue should be created.

[piscisaureus]

@jonathanong

only changed .randomBytes() and .pseudoRandomBytes(). were there others?

Yes, crypto.pbkdf2
Edit: I'm actually no so sure the callback is optional there.

[charmander]

“Please us” → “Please use” for these last two messages.

[jonathanong]

what's the status on this? if desired, i can rebase and reopen for v1.x

[brendanashworth]

I'm pretty sure doc updates would be a necessity to merge this in, but I don't believe a rebase and reopen is necessary, as a contributor would merge it manually anyways (unless there are merge conflicts). I could be corrected on that.