mirror of
https://github.com/sudo-project/sudo.git
synced 2025-09-04 00:05:11 +00:00
no more --with-getpass
This commit is contained in:
@@ -27,16 +27,14 @@ A) Make sure you have an entry in your syslog.conf file to save
|
|||||||
|
|
||||||
Q) When sudo asks me for my password it never accepts what I enter even
|
Q) When sudo asks me for my password it never accepts what I enter even
|
||||||
though I know I entered my password correctly.
|
though I know I entered my password correctly.
|
||||||
A) Try running configure with the --with-getpass option. After this
|
A) If your system uses shadow passwords, it is possible that sudo
|
||||||
when you build sudo it will use the system's getpass() routine instead
|
didn't detect this. Take a look at the generated config.h file
|
||||||
of sudo's own version. If your system uses shadow passwords, it
|
and verify that the C function used for shadow password lookups
|
||||||
is possible that sudo didn't detect this. Take a look at the
|
was detected. For instance, for SVR4-style shadow passwords,
|
||||||
generated config.h file and verify that the C function used for
|
HAVE_GETSPNAM should be defined (you can search for the string
|
||||||
shadow password lookups was detected. For instance, for SVR4-style
|
"shadow passwords" in config.h with your editor). Note that
|
||||||
shadow passwords, HAVE_GETSPNAM should be defined (you can search
|
there is no define for 4.4BSD-based shadow passwords since that
|
||||||
for the string "shadow passwords" in config.h with your editor).
|
just uses the standard getpw* routines.
|
||||||
Note that there is no define for 4.4BSD-based shadow passwords
|
|
||||||
since that just uses the standard getpw* routines.
|
|
||||||
|
|
||||||
Q) I don't want the sudoers file in /etc, how can I specify where it
|
Q) I don't want the sudoers file in /etc, how can I specify where it
|
||||||
should go?
|
should go?
|
||||||
@@ -72,16 +70,8 @@ A) Sudo removes the following "dangerous" environment variables
|
|||||||
_RLD_*
|
_RLD_*
|
||||||
SHLIB_PATH (HP-UX only)
|
SHLIB_PATH (HP-UX only)
|
||||||
LIB_PATH (AIX only)
|
LIB_PATH (AIX only)
|
||||||
KRB_CONF (kerberos only)
|
KRB_CONF (kerb4 only)
|
||||||
|
KRB5_CONFIG (kerb5 only)
|
||||||
Q) I can't get the s/key support to work, whatever I do sudo won't
|
|
||||||
accept my key. I had to run configure with --with-getpass,
|
|
||||||
could that have something to do with it?
|
|
||||||
A) Yes, the s/key support requires that you use tgetpass() since
|
|
||||||
most system getpass()'s only grab eight characters or so
|
|
||||||
and s/key needs much mroe than that. It should be possible
|
|
||||||
to get tgetpass() to work, send mail to sudo-bugs@courtesan.com
|
|
||||||
if you need help.
|
|
||||||
|
|
||||||
Q) I modified parse.lex but the Makefile is not generating a new
|
Q) I modified parse.lex but the Makefile is not generating a new
|
||||||
lex.yy.c.
|
lex.yy.c.
|
||||||
|
Reference in New Issue
Block a user