Annotated edit history of
mkpasswd(1) version 1, including all changes.
View license author blame.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
MKPASSWD |
|
|
2 |
!!!MKPASSWD |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
BUGS |
|
|
8 |
SEE ALSO |
|
|
9 |
AUTHOR |
|
|
10 |
---- |
|
|
11 |
!!NAME |
|
|
12 |
|
|
|
13 |
|
|
|
14 |
mkpasswd - Overfeatured front end to crypt(3) |
|
|
15 |
!!SYNOPSIS |
|
|
16 |
|
|
|
17 |
|
|
|
18 |
__mkpasswd PASSWORD SALT__ |
|
|
19 |
!!DESCRIPTION |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
__mkpasswd__ encrypts the given password with the |
|
|
23 |
__crypt(3)__ libc function using the given |
|
|
24 |
salt. |
|
|
25 |
!!OPTIONS |
|
|
26 |
|
|
|
27 |
|
|
|
28 |
__-S, --salt=STRING__ |
|
|
29 |
|
|
|
30 |
|
|
|
31 |
Use the ''STRING'' as salt. |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
__-H, --hash=TYPE__ |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
Compute the password using the ''TYPE'' algorithm. If |
|
|
38 |
''TYPE'' is missing available algorithms are |
|
|
39 |
printed. |
|
|
40 |
|
|
|
41 |
|
|
|
42 |
__-P, --password-fd=NUM__ |
|
|
43 |
|
|
|
44 |
|
|
|
45 |
Read the password from file descriptor ''NUM'' instead of |
|
|
46 |
using ''getpass(3)''. If the file descriptor is not |
|
|
47 |
connected to a tty then no other message than the hashed |
|
|
48 |
password is printed on stdout. |
|
|
49 |
|
|
|
50 |
|
|
|
51 |
__-s, --stdin__ |
|
|
52 |
|
|
|
53 |
|
|
|
54 |
Like ''--password-fd=0''. |
|
|
55 |
!!BUGS |
|
|
56 |
|
|
|
57 |
|
|
|
58 |
If the ''--stdin'' option is used, passwords containing |
|
|
59 |
some control characters may not be read |
|
|
60 |
correctly. |
|
|
61 |
|
|
|
62 |
|
|
|
63 |
This programs suffers of a bad case of |
|
|
64 |
featuritis. |
|
|
65 |
!!SEE ALSO |
|
|
66 |
|
|
|
67 |
|
|
|
68 |
''passwd(1), passwd(5), crypt(3), |
|
|
69 |
getpass(3)'' |
|
|
70 |
!!AUTHOR |
|
|
71 |
|
|
|
72 |
|
|
|
73 |
__mkpasswd__ and this man page were written by Marco |
|
|
74 |
d'Itri |
|
|
75 |
__ |
|
|
76 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.