Indeed, there's nothing wrong with using node.js' bindings to OpenSSL. It's crypto in the browser which creates the chicken-and-egg problem.