-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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: add --tls-min-v1.2 CLI switch #27520
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
// Flags: --tls-min-v1.2 | ||
'use strict'; | ||
const common = require('../common'); | ||
if (!common.hasCrypto) common.skip('missing crypto'); | ||
|
||
// Check that node `--tls-min-v1.2` is supported. | ||
|
||
const assert = require('assert'); | ||
const tls = require('tls'); | ||
|
||
assert.strictEqual(tls.DEFAULT_MAX_VERSION, 'TLSv1.3'); | ||
assert.strictEqual(tls.DEFAULT_MIN_VERSION, 'TLSv1.2'); | ||
|
||
// Check the min-max version protocol versions against these CLI settings. | ||
require('./test-tls-min-max-version.js'); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As with the other PR, totally not blocking, but using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note that it is the same pattern as the other 4 or 5 tests of TLS CLI options. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with @Trott that this does not seem ideal. I would move the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can see the argument for it not being a fixture. It's test code, not a fixture loaded by a test. And so we want it linted and so on.... Maybe there's some way to abstract it into Anyway, it gives me pause when I see it, but I'm OK with it, especially since it's the way it's already being done.... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (I am going to spend half a second wondering if it should be a fixture every single time I come across it though. 😀) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the
REPLACEME
value be the wrong version given that this has already landed in earlier versions? Should we put the actual11.x
version here now?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
REPLACEME values are only accurate on the release branch they land in (last time I checked).