File: securityissues.html

package info (click to toggle)
abs-guide 10-4
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, forky, sid, trixie
  • size: 6,952 kB
  • sloc: sh: 14,129; makefile: 81
file content (370 lines) | stat: -rw-r--r-- 6,401 bytes parent folder | download | duplicates (3)
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
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Security Issues</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="Advanced Bash-Scripting Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Miscellany"
HREF="miscellany.html"><LINK
REL="PREVIOUS"
TITLE="Assorted Tips"
HREF="assortedtips.html"><LINK
REL="NEXT"
TITLE="Portability Issues"
HREF="portabilityissues.html"><META
HTTP-EQUIV="Content-Style-Type"
CONTENT="text/css"><LINK
REL="stylesheet"
HREF="common/kde-common.css"
TYPE="text/css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=iso-8859-1"><META
HTTP-EQUIV="Content-Language"
CONTENT="en"><LINK
REL="stylesheet"
HREF="common/kde-localised.css"
TYPE="text/css"
TITLE="KDE-English"><LINK
REL="stylesheet"
HREF="common/kde-default.css"
TYPE="text/css"
TITLE="KDE-Default"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#AA0000"
VLINK="#AA0055"
ALINK="#AA0000"
STYLE="font-family: sans-serif;"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Advanced Bash-Scripting Guide: An in-depth exploration of the art of shell scripting</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="assortedtips.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 36. Miscellany</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="portabilityissues.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="SECURITYISSUES"
></A
>36.8. Security Issues</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="INFECTEDSCRIPTS"
></A
>36.8.1. Infected Shell Scripts</H2
><P
><A
NAME="INFECTEDSCRIPTS1"
></A
></P
><P
>A brief warning about script security is indicated.
	  A shell script may contain a <I
CLASS="FIRSTTERM"
>worm</I
>,
	  <I
CLASS="FIRSTTERM"
>trojan</I
>, or even a
	  <I
CLASS="FIRSTTERM"
>virus</I
>. For that reason, never run
	  as <I
CLASS="FIRSTTERM"
>root</I
> a script (or permit it to
	  be inserted into the system startup scripts in <TT
CLASS="FILENAME"
>/etc/rc.d</TT
>) unless you have obtained
	  said script from a trusted source or you have carefully analyzed
	  it to make certain it does nothing harmful.</P
><P
>Various researchers at Bell Labs and other sites, including M.
	  Douglas McIlroy, Tom Duff, and Fred Cohen have investigated the
	  implications of shell script viruses. They conclude that it is
	  all too easy for even a novice, a <SPAN
CLASS="QUOTE"
>"script kiddie,"</SPAN
>
	  to write one.
	    <A
NAME="AEN20748"
HREF="#FTN.AEN20748"
>[1]</A
>
	  </P
><P
>Here is yet another reason to learn scripting. Being able to
	  look at and understand scripts may protect your system from
	  being compromised by a rogue script.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="HIDINGSOURCE"
></A
>36.8.2. Hiding Shell Script Source</H2
><P
>For security purposes, it may be necessary to render a script
	  unreadable. If only there were a utility to create a stripped
	  binary executable from a script. Francisco Rosales' <A
HREF="http://www.datsi.fi.upm.es/~frosal/sources/"
TARGET="_top"
>shc --
	  generic shell script compiler</A
> does exactly that.</P
><P
>Unfortunately, according to <A
HREF="http://www.linuxjournal.com/article/8256"
TARGET="_top"
>an article</A
> in
	 the October, 2005 <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Linux Journal</I
></SPAN
>,
	 the binary can, in at least some cases, be decrypted to recover
	 the original script source. Still, this could be a useful
	 method of keeping scripts secure from all but the most skilled
	 hackers.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="SECURITYTIPS"
></A
>36.8.3. Writing Secure Shell Scripts</H2
><P
><A
NAME="SECURITYTIPS1"
></A
></P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Dan Stromberg</I
></SPAN
> suggests the following
	  guidelines for writing (relatively) secure shell scripts.</P
><P
>         <UL
><LI
><P
>Don't put secret data in <A
HREF="othertypesv.html#ENVREF"
>environment variables</A
>.</P
></LI
><LI
><P
>Don't pass secret data in an external
	      command's arguments (pass them in via a <A
HREF="special-chars.html#PIPEREF"
>pipe</A
> or <A
HREF="io-redirection.html#IOREDIRREF"
>redirection</A
> instead).</P
></LI
><LI
><P
>Set your <A
HREF="variables2.html#PATHREF"
>$PATH</A
>
	      carefully. Don't just trust whatever path you
	      inherit from the caller if your script is running as
	      <I
CLASS="FIRSTTERM"
>root</I
>. In fact, whenever you use
	      an environment variable inherited from the caller, think
	      about what could happen if the caller put something
	      misleading in the variable, e.g., if the caller set
	      <A
HREF="variables2.html#HOMEDIRREF"
>$HOME</A
> to <TT
CLASS="FILENAME"
>/etc</TT
>.</P
></LI
></UL
>
        </P
></DIV
></DIV
><H3
CLASS="FOOTNOTES"
>Notes</H3
><TABLE
BORDER="0"
CLASS="FOOTNOTES"
WIDTH="100%"
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN20748"
HREF="securityissues.html#AEN20748"
>[1]</A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>See Marius van Oers' article, <A
HREF="http://www.virusbtn.com/magazine/archives/200204/malshell.xml"
TARGET="_top"
>Unix
	      Shell Scripting Malware</A
>, and also the
	      <A
HREF="biblio.html#DENNINGREF"
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Denning</I
></SPAN
>
	      reference</A
> in the
	      <I
CLASS="FIRSTTERM"
>bibliography</I
>.</P
></TD
></TR
></TABLE
><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="assortedtips.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="portabilityissues.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Assorted Tips</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="miscellany.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Portability Issues</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>