2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
6 menu "Login/Password Management Utilities"
8 config CONFIG_USE_BB_PWD_GRP
9 bool "Use internal password and group functions rather than system functions"
12 If you leave this disabled, busybox will use the system's password
13 and group functions. And if you are using the GNU C library
14 (glibc), you will then need to install the /etc/nsswitch.conf
15 configuration file and the required /lib/libnss_* libraries in
16 order for the password and group functions to work. This generally
17 makes your embedded system quite a bit larger.
19 Enabling this option will cause busybox to directly access the
20 system's /etc/password, /etc/group files (and your system will be
21 smaller, and I will get fewer emails asking about how glibc NSS
22 works). When this option is enabled, you will not be able to use
23 PAM to access remote LDAP password servers and whatnot. And if you
24 want hostname resolution to work with glibc, you still need the
25 /lib/libnss_* libraries.
27 If you enable this option, it will add about 1.5k to busybox.
30 config CONFIG_ADDGROUP
34 Utility for creating a new group account.
36 config CONFIG_DELGROUP
40 Utility for deleting a group account.
46 Utility for creating a new user account.
52 Utility for deleting a user account.
58 getty lets you log in on a tty, it is normally invoked by init.
64 login is used when signing onto a system.
66 config CONFIG_FEATURE_SECURETTY
67 bool " Support for /etc/securetty"
69 depends on CONFIG_LOGIN
71 The file /etc/securetty is used by (some versions of) login(1).
72 The file contains the device names of tty lines (one per line,
73 without leading /dev/) on which root is allowed to login.
79 passwd changes passwords for user and group accounts. A normal user
80 may only change the password for his/her own account, the super user
81 may change the password for any account. The administrator of a group
82 may change the password for the group.
88 su is used to become another user during a login session.
89 Invoked without a username, su defaults to becoming the super user.
95 sulogin is invoked when the system goes into single user
96 mode (this is done through an entry in inittab).
102 Build the "vlock" applet which allows you to lock (virtual) terminals.
104 comment "Common options for adduser, deluser, login, su"
105 depends on CONFIG_ADDUSER || CONFIG_DELUSER || CONFIG_LOGIN || CONFIG_SU
107 config CONFIG_FEATURE_SHADOWPASSWDS
108 bool "Support for shadow passwords"
110 depends on CONFIG_ADDUSER || CONFIG_DELUSER || CONFIG_LOGIN || CONFIG_SU
112 Build support for shadow password in /etc/shadow. This file is only
113 readable by root and thus the encrypted passwords are no longer
116 config CONFIG_USE_BB_SHADOW
117 bool " Use busybox shadow password functions"
119 depends on CONFIG_USE_BB_PWD_GRP && CONFIG_FEATURE_SHADOWPASSWDS
121 If you leave this disabled, busybox will use the system's shadow
122 password handling functions. And if you are using the GNU C library
123 (glibc), you will then need to install the /etc/nsswitch.conf
124 configuration file and the required /lib/libnss_* libraries in
125 order for the shadow password functions to work. This generally
126 makes your embedded system quite a bit larger.
128 Enabling this option will cause busybox to directly access the
129 system's /etc/shadow file when handling shadow passwords. This
130 makes your system smaller and I will get fewer emails asking about
131 how glibc NSS works). When this option is enabled, you will not be
132 able to use PAM to access shadow passwords from remote LDAP
133 password servers and whatnot.