10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v3_0
v3_1
v3_2
v3_3
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/mips64el
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
| Line | |
|---|
| 1 | <sect2><title>Configuring Shadow Password Suite</title>
|
|---|
| 2 |
|
|---|
| 3 | <para>This package contains the utilities to modify user's passwords, add new
|
|---|
| 4 | users/groups, delete users/groups and more. We're not going to explain
|
|---|
| 5 | what 'password shadowing' means. All about that can be read in the doc/HOWTO
|
|---|
| 6 | file within the unpacked shadow password suite's source tree. There's one
|
|---|
| 7 | thing you should keep in mind, if you decide to use shadow support, that
|
|---|
| 8 | programs that need to verify passwords (examples are xdm, ftp daemons,
|
|---|
| 9 | pop3 daemons, etc) need to be 'shadow-compliant', eg. they need to
|
|---|
| 10 | be able to work with shadow'ed passwords.</para>
|
|---|
| 11 |
|
|---|
| 12 | <para>To enable shadow'ed passwords, run the following command:</para>
|
|---|
| 13 |
|
|---|
| 14 | <para><screen><userinput>/usr/sbin/pwconv</userinput></screen></para>
|
|---|
| 15 |
|
|---|
| 16 | </sect2>
|
|---|
| 17 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
