This file is indexed.

/usr/share/doc/samhain/manual.html/droproot.html is in samhain 3.1.0-5ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  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
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Important installation notes</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Samhain Host Integrity Monitoring System"
HREF="index.html"><LINK
REL="UP"
TITLE="Configuring yule, the log server"
HREF="yule.html"><LINK
REL="PREVIOUS"
TITLE="Configuring yule, the log server"
HREF="yule.html"><LINK
REL="NEXT"
TITLE="Registering a client"
HREF="clients.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="./docbook.css"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/header.html"--><!--#endif --><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Samhain Host Integrity Monitoring System</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="yule.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Configuring <SPAN
CLASS="APPLICATION"
>yule</SPAN
>, the log server</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="clients.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="DROPROOT"
>6.2. Important installation notes</A
></H1
><P
>As of version 1.7.0, <SPAN
CLASS="APPLICATION"
>yule</SPAN
> will
<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>always</I
></SPAN
> drop root privileges after startup and
initialization. You can use a privileged port (port number below
1024), because setting up the listening socket will occur as long as
<SPAN
CLASS="APPLICATION"
>yule</SPAN
> still has root privileges.</P
><P
>There are some special considerations that need to be taken into account
when setting up an installation of <SPAN
CLASS="APPLICATION"
>yule</SPAN
>. In 
particular:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>The unprivileged user</DT
><DD
><P
>	 By default, <B
CLASS="COMMAND"
>configure</B
> will check (in this order)
	 for the existance of a user <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>yule</I
></SPAN
>,
	 <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>daemon</I
></SPAN
>, or <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>nobody</I
></SPAN
>,
	 and use the first match.
	 </P
><P
>	 You can override this with the option
	 <B
CLASS="COMMAND"
>configure 
	 --enable-identity=<TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
></B
>. The
	 user does not need to exist already; the install script
	 knows how to create a new user (on Linux, FreeBSD, NetBSD, 
	 Solaris, HP-UX, OSF1). 
	 </P
><P
>	 After successful installation, you will be asked to run 
	 <B
CLASS="COMMAND"
>make install-user</B
> in order to:
	 (i) create
	 the user that you specified to <B
CLASS="COMMAND"
>configure</B
>
	 if it does not exist already (<B
CLASS="COMMAND"
>make install-user</B
>
	 will check for this), and 
	 (ii) chown/chmod some directories.
	 </P
><P
>	 After running <B
CLASS="COMMAND"
>make install</B
> and 
	 <B
CLASS="COMMAND"
>make install-user</B
>, you should have a sane setup.
	 </P
></DD
><DT
>Logfile directory</DT
><DD
><P
>	 The system logfile directory usually requires root privileges
	 to write there (otherwise log files may easily get corrupted ...).
	 To enable <SPAN
CLASS="APPLICATION"
>yule</SPAN
> to write the log file
	 and the HTML status file, a (sub-)directory should be used
	 that is owned by <SPAN
CLASS="APPLICATION"
>yule</SPAN
>. The
	 <B
CLASS="COMMAND"
>configure</B
> script and the Makefile will do
	 that automatically with the default layout (i.e. a directory
	 <TT
CLASS="FILENAME"
>/var/log/yule</TT
> will be
	 created).
	 </P
></DD
><DT
>Data files</DT
><DD
><P
>	 The data file directory is now owned by root and
	 world readable by default. If you chown it to a suitable
	 <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>group</I
></SPAN
> for the unprivileged
	 <SPAN
CLASS="APPLICATION"
>yule</SPAN
> user, you can make 
	 it group readable only. <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Note that it is not required,
	 and weakens the security, if the data file directory is writeable
	 for the server.</I
></SPAN
>
	 </P
></DD
><DT
>GnuPG signed configuration file</DT
><DD
><P
>	 The unprivileged yule user must have a 
	 <TT
CLASS="FILENAME"
>.gnupg</TT
> subdirectory in
	 its home directory, holding the public keyring with the
	 key to verify the signature.
	 </P
></DD
><DT
>PID file</DT
><DD
><P
>	 The PID file is written with before dropping root privileges.
	 Therefore <SPAN
CLASS="APPLICATION"
>yule</SPAN
> will not be able to
	 overwrite it later (which is a GoodThing), or 
	 remove it upon exit (it will usually
	 be able to recognize and handle a stale PID file on startup).
	 Still, it may be a good idea to remove it after stopping 
	 <SPAN
CLASS="APPLICATION"
>yule</SPAN
>. The provided start/stop scripts
	 for various architectures will handle this.
	 </P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="yule.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="clients.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Configuring <SPAN
CLASS="APPLICATION"
>yule</SPAN
>, the log server</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="yule.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Registering a client</TD
></TR
></TABLE
></DIV
><!--#if expr="! ($HTTP_USER_AGENT = /MSIE/)"--><!--#include virtual="/resources/ssi/footer.html"--><!--#endif --></BODY
></HTML
>