-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
sshd_config: ability to define more than one Port #33
Comments
This doesn't appear to be valid syntax on OpenSSH 6.1 at least:
Can you confirm? |
Oh, ignore that, I misunderstood. This works as you describe, having just run a test - two Port lines get created in the target file. |
Correct, two separate Port lines getting created in the target file is the intent of the request to allow the sshd daemon to listen simultaneously to two separate ports instead of just one. Thanks! |
Excellent :) |
Did I miss something? I see you closed the issue, but I do not see a patch against this... |
It already works this way, I don't think there's any change required? |
Sorry on the delay. You are quite correct... the code is functioning this way. When I first was testing, somehow I got concatenated ports on a single line... But, i cannot replicate that behaviour. When I give it an array of ports or a single port, multiple or single lines are created in the target, respectively. Thanks again! |
Ah ok, no worries. If you come across it again, do let me know. |
It was most excellent that we can specify more than one IPv4/IPv6 address to listen on with sshd. It would be also most helpful to be able to specify an array of ports to listen to that result in an individual configuration line in sshd_config as well. i.e.
sshd_config { 'Port':
value => [ '22', '8022' ],
}
would result in placing the following lines in the sshd_config:
Port 22
Port 24
If there is anything else that you would like to know concerning this, or are looking for a tester should you accept this, please let me know. Thank you!
Jeffrey
The text was updated successfully, but these errors were encountered: