You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 26, 2020. It is now read-only.
Is your feature request related to a problem? Please describe.
Several parameters within the templates for openssh.conf and opensshd.conf are hardcoded such that they can't be modified using this role. It would be better if all of those values were configurable.
In particular, my use case calls for enabling X11 on some systems (via ForwardX11, X11Forwarding, and X11UseLocalhost).
Describe the solution you'd like
Instead of hardcoded lines like ForwardX11 no, change the template files to use variables (something along the lines of ForwardX11 {{ ssh_x11_forwarding }}) and set those variables to default values matching the current hardcoded settings.
Describe alternatives you've considered ssh_custom_options and sshd_custom_options are both provided in defaults/main.yml, but this is an insufficient option, since it yields configuration files with lines that contradict one another.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Several parameters within the templates for
openssh.conf
andopensshd.conf
are hardcoded such that they can't be modified using this role. It would be better if all of those values were configurable.In particular, my use case calls for enabling X11 on some systems (via
ForwardX11
,X11Forwarding
, andX11UseLocalhost
).Describe the solution you'd like
Instead of hardcoded lines like
ForwardX11 no
, change the template files to use variables (something along the lines ofForwardX11 {{ ssh_x11_forwarding }}
) and set those variables to default values matching the current hardcoded settings.Describe alternatives you've considered
ssh_custom_options
andsshd_custom_options
are both provided indefaults/main.yml
, but this is an insufficient option, since it yields configuration files with lines that contradict one another.The text was updated successfully, but these errors were encountered: