1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
|
.\" $OpenBSD: magic.5,v 1.11 2007/05/31 19:20:10 jmc Exp $
.\"
.\" @(#)$FreeBSD: src/usr.bin/file/magic.5,v 1.11 2000/03/01 12:19:39 sheldonh Exp $
.\"
.\" install as magic.4 on USG, magic.5 on V7 or Berkeley systems.
.\"
.\" Copyright (c) Ian F. Darwin 1986-1995.
.\" Software written by Ian F. Darwin and others;
.\" maintained 1995-present by Christos Zoulas and others.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice immediately at the beginning of the file, without modification,
.\" this list of conditions, and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR
.\" ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd $Mdocdate: May 31 2007 $
.Dt MAGIC 5
.Os
.Sh NAME
.Nm magic
.Nd file command's magic number file
.Sh DESCRIPTION
This manual page documents the format of the magic file as
used by the
.Xr file 1
command, version 3.22.
The
.Nm file
command identifies the type of a file using,
among other tests,
a test for whether the file begins with a certain
.Dq magic number .
.Pp
The file
.Pa /etc/magic
specifies what magic numbers are to be tested for,
what message to print if a particular magic number is found,
and additional information to extract from the file.
.Pp
Each line of the file specifies a test to be performed.
A test compares the data starting at a particular offset
in the file with a 1-byte, 2-byte, or 4-byte numeric value or
a string.
If the test succeeds, a message is printed.
The line consists of the following fields:
.Bl -tag -width indent
.It Sy offset
A number specifying the offset, in bytes, into the file of the data
which is to be tested.
.It Sy type
The type of the data to be tested.
The possible values are:
.Bl -tag -width beshort
.It Sy byte
A one-byte value.
.It Sy short
A two-byte value (on most systems) in this machine's native byte order.
.It Sy long
A four-byte value (on most systems) in this machine's native byte order.
.It Sy string
A string of bytes.
.It Sy date
A four-byte value interpreted as a
.Ux
date.
.It Sy beshort
A two-byte value (on most systems) in big-endian byte order.
.It Sy belong
A four-byte value (on most systems) in big-endian byte order.
.It Sy bedate
A four-byte value (on most systems) in big-endian byte order,
interpreted as a
.Ux
date.
.It Sy leshort
A two-byte value (on most systems) in little-endian byte order.
.It Sy lelong
A four-byte value (on most systems) in little-endian byte order.
.It Sy ledate
A four-byte value (on most systems) in little-endian byte order,
interpreted as a
.Ux
date.
.El
.El
.Pp
The numeric types may optionally be followed by
.Ql &
and a numeric value,
to specify that the value is to be AND'ed with the
numeric value before any comparisons are done.
Prepending a
.Sq u
to the type indicates that ordered comparisons should be unsigned.
.Bl -tag -width indent
.It Sy test
The value to be compared with the value from the file.
If the type is
numeric, this value
is specified in C form; if it is a string, it is specified as a C string
with the usual escapes permitted (e.g.,
.Ql \en
for newline).
.It Sy ""
Numeric values
may be preceded by a character indicating the operation to be performed.
It may be
.Ql =
to specify that the value from the file must equal the specified value,
.Ql <
to specify that the value from the file must be less than the specified
value,
.Ql >
to specify that the value from the file must be greater than the specified
value,
.Ql &
to specify that the value from the file must have set all of the bits
that are set in the specified value,
.Ql ^
to specify that the value from the file must have clear any of the bits
that are set in the specified value, or
.Sq x
to specify that any value will match.
If the character is omitted,
it is assumed to be
.Ql = .
.It Sy ""
Numeric values are specified in C form; e.g.,
.Dq 13
is decimal,
.Dq 013
is octal, and
.Dq 0x13
is hexadecimal.
.It Sy ""
For string values, the byte string from the
file must match the specified byte string.
The operators
.Ql = ,
.Ql < ,
and
.Ql >
(but not
.Ql & )
can be applied to strings.
The length used for matching is that of the string argument
in the magic file.
This means that a line can match any string, and
then presumably print that string, by doing
.Ql >\e0
(because all strings are greater than the null string).
.It Sy message
The message to be printed if the comparison succeeds.
If the string
contains a
.Xr printf 3
format specification, the value from the file (with any specified masking
performed) is printed using the message as the format string.
.El
.Pp
Some file formats contain additional information which is to be printed
along with the file type.
A line which begins with the character
.Ql >
indicates additional tests and messages to be printed.
The number of
.Ql >
on the line indicates the level of the test; a line with no
.Ql >
at the beginning is considered to be at level 0.
.Pp
Each line at level
.Em n+1
is under the control of the line at level
.Em n
most closely preceding it in the magic file.
If the test on a line at level
.Em n
succeeds, the tests specified in all the subsequent lines at level
.Em n+1
are performed, and the messages printed if the tests succeed.
The next
line at level
.Em n
terminates this.
.Pp
If the first character following the last
.Ql >
is a
.Ql (
then the string after the parenthesis is interpreted as an indirect offset.
That means that the number after the parenthesis is used as an offset in
the file.
The value at that offset is read, and is used again as an offset
in the file.
.Pp
Indirect offsets are of the form:
.Dq (x[.[bsl]][+-][y]) .
The value of
.Sq x
is used as an offset in the file.
A byte, short or long is read at that offset
depending on the
.Dq [bsl]
type specifier.
To that number the value of
.Sq y
is added and the result is used as an offset in the file.
The default type
if one is not specified is long.
.Pp
Sometimes you do not know the exact offset as this depends on the length of
preceding fields.
You can specify an offset relative to the end of the
last uplevel field (of course this may only be done for sublevel tests, i.e.,
test beginning with
.Ql > ) .
Such a relative offset is specified using
.Ql &
as a prefix to the offset.
.Sh FILES
.Bl -tag -width /etc/magic
.It Pa /etc/magic
.El
.Sh SEE ALSO
.Xr file 1
.Sh BUGS
The formats
.Li long ,
.Li belong ,
.Li lelong ,
.Li short ,
.Li beshort ,
.Li leshort ,
.Li date ,
.Li bedate ,
and
.Li ledate
are system-dependent; perhaps they should be specified as a number
of bytes (2B, 4B, etc),
since the files being recognized typically come from
a system on which the lengths are invariant.
.Pp
There is (currently) no support for specified-endian data to be used in
indirect offsets.
.\"
.\" From: guy@sun.uucp (Guy Harris)
.\" Newsgroups: net.bugs.usg
.\" Subject: /etc/magic's format isn't well documented
.\" Message-ID: <2752@sun.uucp>
.\" Date: 3 Sep 85 08:19:07 GMT
.\" Organization: Sun Microsystems, Inc.
.\" Lines: 136
.\"
.\" Here's a manual page for the format accepted by the "file" made by adding
.\" the changes I posted to the S5R2 version.
.\"
.\" Modified for Ian Darwin's version of the file command.
|