modules/ssh/templates/sshd_config.erb - Issue 5766400081657856: #760 - Make our ssh configuration used automatically for all servers

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments.

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Side by Side Diff: modules/ssh/templates/sshd_config.erb

Issue 5766400081657856: #760 - Make our ssh configuration used automatically for all servers (Closed)

Patch Set: Created July 15, 2014, 11:03 a.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

View unified diff | Download patch

« modules/ssh/manifests/init.pp ('K') | « modules/ssh/manifests/init.pp ('k') | modules/statsclient/manifests/init.pp » ('j') | modules/statsclient/manifests/init.pp » ('J')

OLD	NEW
1 # Package generated configuration file	1 # Package generated configuration file

2 # See the sshd_config(5) manpage for details	2 # See the sshd_config(5) manpage for details

3	3

4 # What ports, IPs and protocols we listen for	4 # What ports, IPs and protocols we listen for

5 Port 22	5 Port 22

6 # Use these options to restrict which interfaces/protocols sshd will bind to	6 # Use these options to restrict which interfaces/protocols sshd will bind to

7 #ListenAddress ::	7 #ListenAddress ::

8 #ListenAddress 0.0.0.0	8 #ListenAddress 0.0.0.0

9 Protocol 2	9 Protocol 2

10 # HostKeys for protocol version 2	10 # HostKeys for protocol version 2

(...skipping 69 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
80	80

81 # Set this to 'yes' to enable PAM authentication, account processing,	81 # Set this to 'yes' to enable PAM authentication, account processing,

82 # and session processing. If this is enabled, PAM authentication will	82 # and session processing. If this is enabled, PAM authentication will

83 # be allowed through the ChallengeResponseAuthentication and	83 # be allowed through the ChallengeResponseAuthentication and

84 # PasswordAuthentication. Depending on your PAM configuration,	84 # PasswordAuthentication. Depending on your PAM configuration,

85 # PAM authentication via ChallengeResponseAuthentication may bypass	85 # PAM authentication via ChallengeResponseAuthentication may bypass

86 # the setting of "PermitRootLogin without-password".	86 # the setting of "PermitRootLogin without-password".

87 # If you just want the PAM account and session checks to run without	87 # If you just want the PAM account and session checks to run without

88 # PAM authentication, then enable this but set PasswordAuthentication	88 # PAM authentication, then enable this but set PasswordAuthentication

89 # and ChallengeResponseAuthentication to 'no'.	89 # and ChallengeResponseAuthentication to 'no'.

90 UsePAM yes	90 UsePAM yes
	Wladimir Palant 2014/07/15 11:56:47 This no longer needs to be a template, move is to This no longer needs to be a template, move is to files/ and use as a static file? mathias 2014/07/15 12:03:12 Well, I could imagine performing some future globa Show quoted text On 2014/07/15 11:56:47, Wladimir Palant wrote: > This no longer needs to be a template, move is to files/ and use as a static > file? Well, I could imagine performing some future global setup by passing class parameters through to the template (e.g. the Max* directives from modules/filtermaster/init.pp). Of course one could argue that we can re-convert it into a template when necessary.. Wladimir Palant 2014/07/15 14:18:35 Well, I cannot - that fragment is being created vi Show quoted text On 2014/07/15 12:03:12, matze wrote: > Well, I could imagine performing some future global setup by passing class > parameters through to the template Well, I cannot - that fragment is being created via base module, we don't have any server-specific parameters at this point so I don't see any reason why we would use templates. Either way, our general approach is not to keep things around just because we might need it at some point.
91	91

92 <%= custom_configuration %>

OLD	NEW