-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tls: docs error regarding dhparam
#958
Comments
cc: @shigeki @indutny |
Reading through |
Yeah, I'm +1 for buffer, though we may need to try to load file anyway, since we are doing it now. Mind helping with this? |
If buffer isn't supported yet, I can add it. Should be easy enough as |
@silverwind Good catch. Yes, it is not a file but |
Sure, will do a PR tomorrow if that's timely enough. You mean that string and buffer are already supported? |
Yes, both is supported. I've just tested it with using |
The docs say:
The fact that this seems to take a file instead of a
buffer
orstring
strikes me odd, as all other TLS options take these types. I've searched a bit and it seems there are nofs
calls to read such a file. I see this inlib/_tls_common.js
:Could it be that the docs are just plainly wrong about this option?
The text was updated successfully, but these errors were encountered: