comparison options.h @ 178:058cc7892636

propagate from branch 'au.asn.ucc.matt.dropbear.nonblock-stdout-stderr' (head 0aee4615c96aea0526736b394455958c1fbb47c9) to branch 'au.asn.ucc.matt.dropbear' (head dff46fd69e33acd167e41dfd18b948a82c5489d1)
author Matt Johnston <matt@ucc.asn.au>
date Sun, 13 Mar 2005 12:03:27 +0000
parents 2098857ab826
children 0d56e4b80dfb
comparison
equal deleted inserted replaced
175:2c5741e4b855 178:058cc7892636
109 #endif 109 #endif
110 110
111 /* Authentication Types - at least one required. 111 /* Authentication Types - at least one required.
112 RFC Draft requires pubkey auth, and recommends password */ 112 RFC Draft requires pubkey auth, and recommends password */
113 113
114 /* PAM auth is quite simple, and only works for PAM modules which just do a 114 /* Note: PAM auth is quite simple, and only works for PAM modules which just do
115 * simple "Login: " "Password: " (or something like that - if your module is 115 * a simple "Login: " "Password: " (you can edit the strings in svr-authpam.c).
116 * similar but not quite like that, edit the strings in svr-authpam.c). 116 * It's useful for systems like OS X where standard password crypts don't work,
117 * Basically, it's useful for systems like OS X where standard password crypts 117 * but there's an interface via a PAM module - don't bother using it otherwise.
118 * don't work, but there's an interface via a PAM module. You'll need to 118 * You can't enable both PASSWORD and PAM. */
119 * configure with --enable-pam as well, since it's off by default. And you
120 * should only enable either PASSWORD _or_ PAM auth, not both. */
121 119
122 #define ENABLE_SVR_PASSWORD_AUTH 120 #define ENABLE_SVR_PASSWORD_AUTH
123 /*#define ENABLE_SVR_PAM_AUTH*/ 121 /*#define ENABLE_SVR_PAM_AUTH*/
124 #define ENABLE_SVR_PUBKEY_AUTH 122 #define ENABLE_SVR_PUBKEY_AUTH
125 123
141 * per session (or more for very long-lived sessions). */ 139 * per session (or more for very long-lived sessions). */
142 140
143 /* If you are lacking entropy on the system then using /dev/urandom 141 /* If you are lacking entropy on the system then using /dev/urandom
144 * will prevent Dropbear from blocking on the device. This could 142 * will prevent Dropbear from blocking on the device. This could
145 * however significantly reduce the security of your ssh connections 143 * however significantly reduce the security of your ssh connections
146 * if the PRNG state becomes simpler. */ 144 * if the PRNG state becomes guessable - make sure you know what you are
145 * doing if you change this. */
147 #define DROPBEAR_RANDOM_DEV "/dev/random" 146 #define DROPBEAR_RANDOM_DEV "/dev/random"
148 147
149 /* prngd must be manually set up to produce output */ 148 /* prngd must be manually set up to produce output */
150 /*#define DROPBEAR_PRNGD_SOCKET "/var/run/dropbear-rng"*/ 149 /*#define DROPBEAR_PRNGD_SOCKET "/var/run/dropbear-rng"*/
151 150
188 /******************************************************************* 187 /*******************************************************************
189 * You shouldn't edit below here unless you know you need to. 188 * You shouldn't edit below here unless you know you need to.
190 *******************************************************************/ 189 *******************************************************************/
191 190
192 #ifndef DROPBEAR_VERSION 191 #ifndef DROPBEAR_VERSION
193 #define DROPBEAR_VERSION "0.44" 192 #define DROPBEAR_VERSION "0.45"
194 #endif 193 #endif
195 194
196 #define LOCAL_IDENT "SSH-2.0-dropbear_" DROPBEAR_VERSION 195 #define LOCAL_IDENT "SSH-2.0-dropbear_" DROPBEAR_VERSION
197 #define PROGNAME "dropbear" 196 #define PROGNAME "dropbear"
198 197