mtree.8 (36841) | mtree.8 (44303) |
---|---|
1.\" Copyright (c) 1989, 1990, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" From: @(#)mtree.8 8.2 (Berkeley) 12/11/93 | 1.\" Copyright (c) 1989, 1990, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" From: @(#)mtree.8 8.2 (Berkeley) 12/11/93 |
33.\" $Id: mtree.8,v 1.12 1998/06/05 14:43:40 peter Exp $ | 33.\" $Id: mtree.8,v 1.13 1998/06/10 06:45:08 peter Exp $ |
34.\" | 34.\" |
35.Dd February 9, 1995 | 35.Dd February 26, 1999 |
36.Dt MTREE 8 37.Os 38.Sh NAME 39.Nm mtree 40.Nd map a directory hierarchy 41.Sh SYNOPSIS 42.Nm mtree 43.Op Fl cdeinrUux --- 90 unchanged lines hidden (view full) --- 134.It Cm ignore 135Ignore any file hierarchy below this file. 136.It Cm gid 137The file group as a numeric value. 138.It Cm gname 139The file group as a symbolic name. 140.It Cm md5digest 141The MD5 message digest of the file. | 36.Dt MTREE 8 37.Os 38.Sh NAME 39.Nm mtree 40.Nd map a directory hierarchy 41.Sh SYNOPSIS 42.Nm mtree 43.Op Fl cdeinrUux --- 90 unchanged lines hidden (view full) --- 134.It Cm ignore 135Ignore any file hierarchy below this file. 136.It Cm gid 137The file group as a numeric value. 138.It Cm gname 139The file group as a symbolic name. 140.It Cm md5digest 141The MD5 message digest of the file. |
142.It Cm sha1digest 143The 144.Tn FIPS 145160-1 146.Pq Dq Tn SHA-1 147message digest of the file. 148.It Cm ripemd160digest 149The 150.Tn RIPEMD160 151message digest of the file. |
|
142.It Cm mode 143The current file's permissions as a numeric (octal) or symbolic 144value. 145.It Cm nlink 146The number of hard links the file is expected to have. 147.It Cm nochange 148Make sure this file or directory exists but otherwise ignore all attributes. 149.It Cm uid --- 85 unchanged lines hidden (view full) --- 235A status of 2 is converted to a status of 0 if the 236.Fl U 237option is used. 238.Sh EXAMPLES 239To detect system binaries that have been ``trojan horsed'', it is recommended 240that 241.Nm 242.Fl K | 152.It Cm mode 153The current file's permissions as a numeric (octal) or symbolic 154value. 155.It Cm nlink 156The number of hard links the file is expected to have. 157.It Cm nochange 158Make sure this file or directory exists but otherwise ignore all attributes. 159.It Cm uid --- 85 unchanged lines hidden (view full) --- 245A status of 2 is converted to a status of 0 if the 246.Fl U 247option is used. 248.Sh EXAMPLES 249To detect system binaries that have been ``trojan horsed'', it is recommended 250that 251.Nm 252.Fl K |
243.Cm md5digest | 253.Cm sha1digest |
244be run on the file systems, and a copy of the results stored on a different 245machine, or, at least, in encrypted form. 246The output file itself should be digested using the 247.Xr md5 1 248utility. 249Then, periodically, 250.Nm 251and --- 28 unchanged lines hidden (view full) --- 280.Xr fts 3 , 281.Xr md5 3 , 282.Xr chown 8 283.Sh HISTORY 284The 285.Nm 286utility appeared in 287.Bx 4.3 Reno . | 254be run on the file systems, and a copy of the results stored on a different 255machine, or, at least, in encrypted form. 256The output file itself should be digested using the 257.Xr md5 1 258utility. 259Then, periodically, 260.Nm 261and --- 28 unchanged lines hidden (view full) --- 290.Xr fts 3 , 291.Xr md5 3 , 292.Xr chown 8 293.Sh HISTORY 294The 295.Nm 296utility appeared in 297.Bx 4.3 Reno . |
288The MD5 digest capability was added in | 298The 299.Tn MD5 300digest capability was added in |
289.Fx 2.1 , 290in response to the widespread use of programs which can spoof 291.Xr cksum 1 . | 301.Fx 2.1 , 302in response to the widespread use of programs which can spoof 303.Xr cksum 1 . |
292 | 304The 305.Tn SHA-1 306and 307.Tn RIPEMD160 308digests were added in 309.Fx 4.0 , 310as new attacks have demonstrated weaknesses in 311.Tn MD5 . |