summaryrefslogtreecommitdiff
path: root/sshd_config
diff options
context:
space:
mode:
authorDarren Tucker <dtucker@zip.com.au>2013-09-18 15:09:38 +1000
committerDarren Tucker <dtucker@zip.com.au>2013-09-18 15:09:38 +1000
commite90a06ae570fd259a2f5ced873c7f17390f535a5 (patch)
tree4d09dd24b667049a7dd27f3226f7ed5d06d6d368 /sshd_config
parent13840e0103946982cee2a05c40697be7e57dca41 (diff)
- (dtucker) [sshd_config] Trailing whitespace; from jstjohn at purdue edu.
Diffstat (limited to 'sshd_config')
-rw-r--r--sshd_config4
1 files changed, 2 insertions, 2 deletions
diff --git a/sshd_config b/sshd_config
index 8d8eeea34..dbda7491e 100644
--- a/sshd_config
+++ b/sshd_config
@@ -84,8 +84,8 @@ AuthorizedKeysFile .ssh/authorized_keys
84#GSSAPIAuthentication no 84#GSSAPIAuthentication no
85#GSSAPICleanupCredentials yes 85#GSSAPICleanupCredentials yes
86 86
87# Set this to 'yes' to enable PAM authentication, account processing, 87# Set this to 'yes' to enable PAM authentication, account processing,
88# and session processing. If this is enabled, PAM authentication will 88# and session processing. If this is enabled, PAM authentication will
89# be allowed through the ChallengeResponseAuthentication and 89# be allowed through the ChallengeResponseAuthentication and
90# PasswordAuthentication. Depending on your PAM configuration, 90# PasswordAuthentication. Depending on your PAM configuration,
91# PAM authentication via ChallengeResponseAuthentication may bypass 91# PAM authentication via ChallengeResponseAuthentication may bypass