1From b8cece92ba19aa77ac013ea161bfe4c7147747c9 Mon Sep 17 00:00:00 2001 2From: Jussi Kukkonen <jussi.kukkonen@intel.com> 3Date: Wed, 2 Dec 2015 11:36:02 +0200 4Subject: Enable pam 5 6We need modify file default_options.h besides enabling pam in 7configure if we want dropbear to support pam. 8 9Upstream-Status: Pending 10 11Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> 12Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> 13--- 14 default_options.h | 4 ++-- 15 1 file changed, 2 insertions(+), 2 deletions(-) 16 17diff --git a/default_options.h b/default_options.h 18index 3b75eb8..8617cd0 100644 19--- a/default_options.h 20+++ b/default_options.h 21@@ -179,7 +179,7 @@ group1 in Dropbear server too */ 22 23 /* Authentication Types - at least one required. 24 RFC Draft requires pubkey auth, and recommends password */ 25-#define DROPBEAR_SVR_PASSWORD_AUTH 1 26+#define DROPBEAR_SVR_PASSWORD_AUTH 0 27 28 /* Note: PAM auth is quite simple and only works for PAM modules which just do 29 * a simple "Login: " "Password: " (you can edit the strings in svr-authpam.c). 30@@ -187,7 +187,7 @@ group1 in Dropbear server too */ 31 * but there's an interface via a PAM module. It won't work for more complex 32 * PAM challenge/response. 33 * You can't enable both PASSWORD and PAM. */ 34-#define DROPBEAR_SVR_PAM_AUTH 0 35+#define DROPBEAR_SVR_PAM_AUTH 1 36 37 /* ~/.ssh/authorized_keys authentication */ 38 #define DROPBEAR_SVR_PUBKEY_AUTH 1 39 40-- 412.1.4 42 43