If PasswordAuthentication is disabled, then offer to disable

ChallengeResponseAuthentication too. The current PAM code will attempt
password-style authentication if ChallengeResponseAuthentication is enabled
(closes: #250369).

1 files changed, 29 insertions, 1 deletions

diff --git a/debian/po/tr.po b/debian/po/tr.po
index b40fcb2b2..af8a0a9a2 100644
--- a/debian/po/tr.po
+++ b/debian/po/tr.po
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: ssh\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2004-03-06 17:54+0000\n"
+"POT-Creation-Date: 2004-10-05 20:41+0100\n"
 "PO-Revision-Date: 2004-04-27 06:50+0300\n"
 "Last-Translator: Recai Oktaş <roktas@omu.edu.tr>\n"
 "Language-Team: Turkish <debian-l10n-turkish@lists.debian.org>\n"
@@ -353,3 +353,31 @@ msgstr ""
 "Bu seçeneği tekrar etkinleştirmek için, sshd_config(5) kılavuz sayfasındaki "
 "uyarı notunu dikkate alarak, sshd yükseltmesi tamamlandığında /etc/ssh/"
 "ssh_config dosyasında \"PermitUserEnvironment yes\" satırını kullanın."
+
+#. Type: boolean
+#. Description
+#: ../templates.master:130
+msgid "Disable challenge-response authentication?"
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates.master:130
+msgid ""
+"Password authentication appears to be disabled in your current OpenSSH "
+"server configuration. In order to prevent users from logging in using "
+"passwords (perhaps using only public key authentication instead) with recent "
+"versions of OpenSSH, you must disable challenge-response authentication, or "
+"else ensure that your PAM configuration does not allow Unix password file "
+"authentication."
+msgstr ""
+
+#. Type: boolean
+#. Description
+#: ../templates.master:130
+msgid ""
+"If you disable challenge-response authentication (the default answer), then "
+"users will not be able to log in using passwords. If you leave it enabled, "
+"then the 'PasswordAuthentication no' option will have no useful effect "
+"unless you also adjust your PAM configuration in /etc/pam.d/ssh."
+msgstr ""