Mercurial > dropbear

comparison options.h @ 121:9337c9f9a607 private-rez

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
PAM improvements
author Matt Johnston <matt@ucc.asn.au>
date Tue, 14 Sep 2004 12:51:16 +0000
parents 3394a7cb30cd
children 8c08fd2b7f5b
comparison
equal deleted inserted replaced
119:3394a7cb30cd 121:9337c9f9a607
108 /* The MOTD file path */ 108 /* The MOTD file path */
109 #ifndef MOTD_FILENAME 109 #ifndef MOTD_FILENAME
110 #define MOTD_FILENAME "/etc/motd" 110 #define MOTD_FILENAME "/etc/motd"
111 #endif 111 #endif
112 112
113 /* Authentication types to enable, at least one required. 113 /* Authentication Types - at least one required.
114 RFC Draft requires pubkey auth, and recommends password */ 114 RFC Draft requires pubkey auth, and recommends password */
115
116 /* PAM auth is quite simple, and only works for PAM modules which just do a
117 * simple "Login: " "Password: " (or something like that - if your module is
118 * similar but not quite like that, edit the strings in svr-authpam.c).
119 * Basically, it's useful for systems like OS X where standard password crypts
120 * don't work, but there's and interface via a PAM module. You'll need to
121 * configure with --enable-pam as well, since it's off by default. And you
122 * should only enable either PASSWORD _or_ PAM auth, not both. */
123
115 /*#define ENABLE_SVR_PASSWORD_AUTH*/ 124 /*#define ENABLE_SVR_PASSWORD_AUTH*/
116 /* Only set PAM auth if you aren't using SVR_PASSWORD_AUTH. Also, you'll need
117 * to make sure PAM libraries etc are installed. To the client, PAM auth looks
118 * just like password auth. */
119 #define ENABLE_SVR_PAM_AUTH 125 #define ENABLE_SVR_PAM_AUTH
120 #define ENABLE_SVR_PUBKEY_AUTH 126 #define ENABLE_SVR_PUBKEY_AUTH
121 127
122 #define ENABLE_CLI_PASSWORD_AUTH 128 #define ENABLE_CLI_PASSWORD_AUTH
123 #define ENABLE_CLI_PUBKEY_AUTH 129 #define ENABLE_CLI_PUBKEY_AUTH