version 1, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
MD5SUM |
| |
|
2 |
!!!MD5SUM |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
BUGS |
| |
|
7 |
AUTHOR |
| |
|
8 |
---- |
| |
|
9 |
!!NAME |
| |
|
10 |
|
| |
|
11 |
|
| |
|
12 |
md5sum - generates or checks MD5 message digests |
| |
|
13 |
!!SYNOPSIS |
| |
|
14 |
|
| |
|
15 |
|
| |
|
16 |
__md5sum__ [[-bv] [[-c [[file]] | [[file...] |
| |
|
17 |
!!DESCRIPTION |
| |
|
18 |
|
| |
|
19 |
|
| |
|
20 |
__md5sum__ generates or checks MD5 checksums. The |
| |
|
21 |
algorithm to generate the checksum is reasonably fast and |
| |
|
22 |
strong enough for most cases. Exact specification of the |
| |
|
23 |
algorithm is in ''RFC 1321.'' |
| |
|
24 |
|
| |
|
25 |
|
| |
|
26 |
Normally __md5sum__ generates checksums of all files |
| |
|
27 |
given to it as a parameter and prints the checksums followed |
| |
|
28 |
by the filenames. If, however, __-c__ is specified, only |
| |
|
29 |
one filename parameter is allowed. This file should contain |
| |
|
30 |
checksums and filenames to which these checksums refer to, |
| |
|
31 |
and the files listed in that file are checked against the |
| |
|
32 |
checksums listed there. See option __-c__ for more |
| |
|
33 |
information. |
| |
|
34 |
|
| |
|
35 |
|
| |
|
36 |
__OPTIONS__ |
| |
|
37 |
|
| |
|
38 |
|
| |
|
39 |
__-b__ |
| |
|
40 |
|
| |
|
41 |
|
| |
|
42 |
Use binary mode. In unix environment, only difference |
| |
|
43 |
between this and the normal mode is an asterix preceding the |
| |
|
44 |
filename in the output. |
| |
|
45 |
|
| |
|
46 |
|
| |
|
47 |
__-c__ |
| |
|
48 |
|
| |
|
49 |
|
| |
|
50 |
Check md5sum of all files listed in ''file'' against the |
| |
|
51 |
checksum listed in the same file. The actual format of that |
| |
|
52 |
file is the same as output of __md5sum.__ That is, each |
| |
|
53 |
line in the file describes a file. A line looks |
| |
|
54 |
like: |
| |
|
55 |
|
| |
|
56 |
|
| |
|
57 |
____ |
| |
|
58 |
|
| |
|
59 |
|
| |
|
60 |
So, for example, if a file was created and its message |
| |
|
61 |
digest calculated like so: |
| |
|
62 |
|
| |
|
63 |
|
| |
|
64 |
__echo foo |
| |
|
65 |
__ |
| |
|
66 |
|
| |
|
67 |
|
| |
|
68 |
__md5sum__ would report: |
| |
|
69 |
|
| |
|
70 |
|
| |
|
71 |
__d3b07384d113edec49eaa6238ad5ff00 |
| |
|
72 |
md5-test-file__ |
| |
|
73 |
|
| |
|
74 |
|
| |
|
75 |
__-v__ |
| |
|
76 |
|
| |
|
77 |
|
| |
|
78 |
Be more verbose. Print filenames when checking (with |
| |
|
79 |
-c). |
| |
|
80 |
!!BUGS |
| |
|
81 |
|
| |
|
82 |
|
| |
|
83 |
The related MD4 message digest algorithm was broken in |
| |
|
84 |
October 1995. MD5 isn't looking as secure as it used |
| |
|
85 |
to. |
| |
|
86 |
|
| |
|
87 |
|
| |
|
88 |
This manpage is not quite accurate and has formatting |
| |
|
89 |
inconsistent with other manpages. |
| |
|
90 |
|
| |
|
91 |
|
| |
|
92 |
__md5sum__ does not accept standard options like |
| |
|
93 |
__--help__. |
| |
|
94 |
!!AUTHOR |
| |
|
95 |
|
| |
|
96 |
|
| |
|
97 |
__md5sum__ was originally written by Branko Lankester, |
| |
|
98 |
and modified afterwards by Colin Plumb and Ian Jackson |
| |
|
99 |
(ijackson@gnu.ai.mit.edu). Manual page was added by Juho |
| |
|
100 |
Vuori (javuori@cc.helsinki.fi) |
| |
|
101 |
---- |
