/usr/share/doc/user-mode-linux-doc/html/honeypots.html is in user-mode-linux-doc 20060501-1.
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 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
<meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<title>UML as a honeypot</title>
</head>
<body alink="#FF0000" vlink="#55188A" link="#0000EF" bgcolor="#FFFFFF" text="#000099">
<table border="0">
<tr align="left">
<td valign="top">
<table border="0">
<tr align="left"><td valign="top" >
<img src="uml-small.png" height="171" width="120"/>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">
<font size="-1"><a href="index.html">Site Home Page</a></font>
<br>
<font size="-1"><a href="http://uml.harlowhill.com">The UML Wiki</a></font>
<br>
<font size="-1"><a href="http://usermodelinux.org">UML Community Site</a></font>
<br>
<font size="-1"><a href="roadmap.html">The UML roadmap</a></font>
<br>
<font size="-1"><a href="uses.html">What it's good for</a></font>
<br>
<font size="-1"><a href="case-studies.html">Case Studies</a></font>
<br>
<font size="-1"><a href="kernel.html">Kernel Capabilities</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/dl-sf.html">Downloading it</a></font>
<br>
<font size="-1"><a href="run.html">Running it</a></font>
<br>
<font size="-1"><a href="compile.html">Compiling</a></font>
<br>
<font size="-1"><a href="install.html">Installation</a></font>
<br>
<font size="-1"><a href="skas.html">Skas Mode</a></font>
<br>
<font size="-1"><a href="patches.html">Incremental Patches</a></font>
<br>
<font size="-1"><a href="tests.html">Test Suite</a></font>
<br>
<font size="-1"><a href="devanon.html">Host memory use</a></font>
<br>
<font size="-1"><a href="fs_making.html">Building filesystems</a></font>
<br>
<font size="-1"><a href="faq.html">Troubles</a></font>
<br>
<font size="-1"><a href="contrib.html">User Contributions</a></font>
<br>
<font size="-1"><a href="links.html">Related Links</a></font>
<br>
<font size="-1"><a href="todo.html">The ToDo list</a></font>
<br>
<font size="-1"><a href="projects.html">Projects</a></font>
<br>
<font size="-1"><a href="diary.html">Diary</a></font>
<br>
<font size="-1"><a href="thanks.html">Thanks</a></font>
<br>
<font size="-1"><a href="contacts.html">Contacts</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Tutorials<br>
<font size="-1"><a href="UserModeLinux-HOWTO.html">The HOWTO (html)</a></font>
<br>
<font size="-1"><a href="UserModeLinux-HOWTO.txt.gz">The HOWTO (text)</a></font>
<br>
<font size="-1"><a href="hostfs.html">Host file access</a></font>
<br>
<font size="-1"><a href="input.html">Device inputs</a></font>
<br>
<font size="-1"><a href="shared_fs.html">Sharing filesystems</a></font>
<br>
<font size="-1"><a href="fs.html">Creating filesystems</a></font>
<br>
<font size="-1"><a href="resize.html">Resizing filesystems</a></font>
<br>
<font size="-1"><a href="networking.html">Virtual Networking</a></font>
<br>
<font size="-1"><a href="mconsole.html">Management Console</a></font>
<br>
<font size="-1"><a href="debugging.html">Kernel Debugging</a></font>
<br>
<font size="-1"><a href="honeypots.html">UML Honeypots</a></font>
<br>
<font size="-1"><a href="gprof.html">gprof and gcov</a></font>
<br>
<font size="-1"><a href="xtut.html">Running X</a></font>
<br>
<font size="-1"><a href="trouble.html">Diagnosing problems</a></font>
<br>
<font size="-1"><a href="config.html">Configuration</a></font>
<br>
<font size="-1"><a href="slack_readme.html">Installing Slackware</a></font>
<br>
<font size="-1"><a href="arch-port.html">Porting UML</a></font>
<br>
<font size="-1"><a href="iomem.html">IO memory emulation</a></font>
<br>
<font size="-1"><a href="2G-2G.html">UML on 2G/2G hosts</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/lksct/index.html">Adding a UML system call</a></font>
<br>
<font size="-1"><a href="nesting.html">Running nested UMLs</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">How you can help<br>
<font size="-1"><a href="help-gen.html">Overview</a></font>
<br>
<font size="-1"><a href="help-doc.html">Documentation</a></font>
<br>
<font size="-1"><a href="help-userspace.html">Utilities</a></font>
<br>
<font size="-1"><a href="help-kernel-v1.html">Kernel bugs</a></font>
<br>
<font size="-1"><a href="projects.html">Kernel projects</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Screenshots<br>
<font size="-1"><a href="net.html">A virtual network</a></font>
<br>
<font size="-1"><a href="x.html">An X session</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Transcripts<br>
<font size="-1"><a href="login.html">A login session</a></font>
<br>
<font size="-1"><a href="debug-session.html">A debugging session</a></font>
<br>
<font size="-1"><a href="slackinst.html">Slackware installation</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Reference<br>
<font size="-1"><a href="switches.html">Kernel switches</a></font>
<br>
<font size="-1"><a href="slack_readme.html">Slackware README</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Papers<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2000/index.html">ALS 2000 paper (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2000.tex">ALS 2000 paper (TeX)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/als2000/slides.html">ALS 2000 slides</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lca2001/lca.html">LCA 2001 slides</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ols2001/index.html">OLS 2001 paper (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/ols2001.tex">OLS 2001 paper (TeX)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2001/index.html">ALS 2001 paper (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2001.tex">ALS 2001 paper (TeX)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ists2002/umlsec.htm">UML security (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lca2002/lca2002.htm">LCA 2002 (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/wvu2002/wvu2002.htm">WVU 2002 (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ists_rt/ists_rt.htm">Security Roundtable (html)</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ols2002/ols2002.html">OLS 2002 slides</a></font>
<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lwe2005/LWE2005.html">LWE 2005 slides</a></font>
</td></tr>
<tr align="left"><td valign="top" bgcolor="#e0e0e0">Fun and Games<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/cgi-bin/hangman">Kernel Hangman</a></font>
<br>
<font size="-1"><a href="sdotm.html">Disaster of the Month</a></font>
</td></tr>
</table>
</td>
<td valign="top" align="left">
<center>
<h3>UML as a honeypot</h3>
</center>
<a name="What is a honeypot?"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">What is a honeypot?</font>
</b>
</td>
</tr>
</table>
<blockquote head="What is a honeypot?">
A honeypot is a sacrificial system that's (usually) made vulnerable,
and put on the net for nasty people to break into. A properly
constructed honeypot is put on a network which closely monitors the
traffic to and from the honeypot. This data can be used for a variety
of purposes
<ul>
<li>
Forensics - analyzing new attacks and exploits
</li>
<li>
Trend analysis - look for changes over time of types of attacks,
techniques, etc
</li>
<li>
Identification - track the bad guys back to their home machines to
figure out who they are
</li>
<li>
Sociology - learn about the bad guys as a group by snooping on email,
IRC traffic, etc which happens to traverse the honeypot
</li>
</ul>
Traditionally, honeypots have been physical systems on a dedicated
network which also contains multiple machines for monitoring the
honeypot and collecting logs from it. This is a huge logistical pain
and prevented honeypots from becoming a common network security tool.
<p>
The advent of virtual machines such as UML has made setting up
honeypots far easier. Instead of a set of physical machines, the
honeypot is now a virtual machine with the host filtering and
monitoring network traffic and collecting logs. Even better, one host
can have multiple honeypots running on it, those honeypots can be
configured in a realistic virtual network, and they can be distributed
on a CD rather than a truck.
<p>
For more information about honeypots (and honeynets) in general, see
<a href="http://www.honeynet.org">honeynet.org</a>.
</blockquote>
<a name="UML honeypot support"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">UML honeypot support</font>
</b>
</td>
</tr>
</table>
<blockquote head="UML honeypot support">
Because of the interest from the honeypot people in UML (and support
from <a href="http://ists.dartmouth.edu">Dartmouth
ISTS</a>), a number of features have been added to UML in order to
make it more useful as a honeypot.
<p>
These include
<ul>
<li>
tty logging - secure logging of all UML tty traffic to the host
</li>
<li>
hppfs - a UML filesystem which allows entries in the UML /proc to be
arbitrarily rewritten from the host, making it possible to make the
UML pretend to be a physical box
</li>
<li>
skas mode - UML can operate in a mode which creates process address
spaces which are identical to the host
</li>
</ul>
</blockquote>
<a name="tty logging"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">tty logging</font>
</b>
</td>
</tr>
</table>
<blockquote head="tty logging">
A problem with physical honeypots is that it's hard to capture
keystrokes. If the bad guys are using ssh to reach the honeypot (and
they probably are since they tend to be very security-conscious),
sniffing the network doesn't help since that traffic is encrypted.
So, you need to capture keystrokes by running something on the
honeypot. This is problematic since you have to assume that it has
been thoroughly compromised, so the logging mechanism may also have
been compromised.
<p>
There are various kernel patches and other kludges (such as an
instrumented bash) to implement tty logging on physical honeypots.
They all suffer from the problem that they can be subverted or
disabled if their presence becomes known to the intruder.
<p>
UML solves this problem with a patch to the tty driver which logs all
traffic through tty devices out to the host. In contrast to the
physical honeypot logging mechanisms, this is undetectable and
unsubvertable. It causes no network traffic or anything else which
can be detected from within the honeypot. It's also in the UML
kernel, which means it can't be defeated by anything the intruder
might do.
<p>
For more information on UML's tty logging, see
<a href="tty_logging.html">this page</a>.
</blockquote>
<a name="hppfs"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">hppfs</font>
</b>
</td>
</tr>
</table>
<blockquote head="hppfs">
The single largest weakness of UML as a honeypot is that it is easy to
for a user to tell that it is a UML rather than a physical machine.
The best sources of information that can be used to distinguish UML
from a physical honeypot is /proc. Files such as /proc/mounts,
/proc/interruppts, and /proc/cmdline contain very UML-specific
information.
<p>
To lessen the danger of a UML honeypot being fingerprinted by an
intruder in this way, the UML /proc can be covered over by a special
filesystem which allows /proc entries to be changed from the host.
The UML hppfs ("HoneyPot ProcFS") filesystem allows /proc entries to
be added or deleted, and for existing entries to be replaced or
modified.
<p>
See <a href="hppfs.html">this page</a> for
information on setting up and customizing a fake /proc using hppfs.
</blockquote>
<a name="skas mode"/><table width="100%" bgcolor="#e0e0e0">
<tr>
<td>
<b>
<font color="black">skas mode</font>
</b>
</td>
</tr>
</table>
<blockquote head="skas mode">
A major weakness of UML in security-related applications, including
honeypots, has been its overall architecture. UML has loaded itself
into the top .5G of its process' address spaces, leaving the remainder
to the process. Thus, the UML kernel, including all of its data, is
accessible to UML processes. And, by default, that data is also
writeable by UML processes. For any security-related application, for
which UML must be a secure jail for root, the fact that the data can
be written is a big problem. For honeypots, the mere fact that the
UML kernel is visible, is a big problem. An intruder can test whether
a honeypot is a UML simply by looking at the top of its address space.
<p>
To address this problem, UML was recently reworked to allow it to run
in a mode in which the UML kernel is in a totally separate host
address space from its processes. This makes the UML kernel binary
and data totally invisible to its processes, and to anyone logged in
to it. It also makes UML kernel data secure from tampering by its
processes.
<p>
This new mode (called "skas", for "Separate Kernel Address Space" -
the old mode is retrospectively called "tt", for "Tracing Thread")
therefore makes a far better honeypot than tt mode. The one
disadvantage is that it requires a patch to the host kernel in order
to run. This patch is available as the latest host-skas patch from
<a href="dl-sf.html">here</a>.
<p>
UML must have CONFIG_MODE_SKAS enabled. It will check for the
presence of the patch on the host and use skas mode if possible. If
you see the following messages at the start of the boot log, UML is
running in skas mode:
<tt>
<pre>
<font size="-1">
Checking for the skas3 patch in the host...found
Checking for /proc/mm...found
</font>
</pre>
</tt>
As a side benefit, you will notice that skas mode, which is secure, is
noticably faster than tt mode, which is not. Furthermore, skas mode
is roughly an order of magnitude faster than tt's "jail" mode, which
is how you previously needed to get the same level of security offered
by skas mode.
<p>
More information on skas mode is available
<a href="skas.html">here</a>.
</blockquote>
</td>
</tr>
</table>
<center>
<font size="-1">Hosted at </font>
<a href="http://sourceforge.net">
<img src="http://sourceforge.net/sflogo.php?group_id=429" width="88" height="31" border="0" alt="SourceForge Logo">
</a>
</center>
</body>
</html>
|