Closed dertseha closed 8 years ago
This is actually a bug in node-openid, which seems similar to this one: https://github.com/havard/node-openid/issues/95
Once that dependency is updated for compatibility with node 0.10.x, passport-openid should be good to go.
gah - sorry, issue posted at wrong project. I should go to sleep ;) But thank you for referencing.
No worries. Ping me here if I need to change any dependencies once a new openid module is published to npm.
The fix has been pushed: https://github.com/havard/node-openid/issues/95#issuecomment-15587983 As passport-openid is dependent on 0.5.x, this update is covered. Thank you!
As per http://nodejs.org/docs/v0.10.0/api/crypto.html#crypto_recent_api_changes , the crypto API now defaults to buffer objects instead of binary.