1
1
<?xml version="1.0" encoding="UTF-8"?>
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
<!ENTITY TIMESTAMP "2019-04-10">
4
<!ENTITY TIMESTAMP "2011-10-03">
5
5
<!ENTITY % common SYSTEM "common.ent">
68
60
The computers run a small client program in the initial RAM disk
69
61
environment which will communicate with a server over a network.
70
62
All network communication is encrypted using TLS. The clients
71
are identified by the server using a TLS public key; each client
63
are identified by the server using an OpenPGP key; each client
72
64
has one unique to it. The server sends the clients an encrypted
73
65
password. The encrypted password is decrypted by the clients
74
using a separate OpenPGP key, and the password is then used to
66
using the same OpenPGP key, and the password is then used to
75
67
unlock the root file system, whereupon the computers can
76
68
continue booting normally.
80
72
<refsect1 id="introduction">
81
73
<title>INTRODUCTION</title>
83
<!-- This paragraph is a combination and paraphrase of two
84
quotes from the 1995 movie “The Usual Suspects”. -->
85
75
You know how it is. You’ve heard of it happening. The Man
86
76
comes and takes away your servers, your friends’ servers, the
87
77
servers of everybody in the same hosting facility. The servers
133
123
So, at boot time, the Mandos client will ask for its encrypted
134
data over the network, decrypt it to get the password, use the
135
password to decrypt the root file system, and continue booting.
124
data over the network, decrypt it to get the password, use it to
125
decrypt the root file, and continue booting.
138
128
Now, of course the initial RAM disk image is not on the
144
134
long, and will no longer give out the encrypted key. The timing
145
135
here is the only real weak point, and the method, frequency and
146
136
timeout of the server’s checking can be adjusted to any desired
150
140
(The encrypted keys on the Mandos server is on its normal file
202
192
No. The server only gives out the passwords to clients which
203
193
have <emphasis>in the TLS handshake</emphasis> proven that
204
they do indeed hold the private key corresponding to that
209
<refsect2 id="sniff">
210
<title>How about sniffing the network traffic and decrypting it
211
later by physically grabbing the Mandos client and using its
214
We only use <acronym>PFS</acronym> (Perfect Forward Security)
215
key exchange algorithms in TLS, which protects against this.
194
they do indeed hold the OpenPGP private key corresponding to
237
<refsect2 id="fakecheck">
238
<title>Faking checker results?</title>
217
<refsect2 id="fakeping">
218
<title>Faking ping replies?</title>
240
If the Mandos client does not have an SSH server, the default
241
is for the Mandos server to use
220
The default for the server is to use
242
221
<quote><literal>fping</literal></quote>, the replies to which
243
222
could be faked to eliminate the timeout. But this could
244
223
easily be changed to any shell command, with any security
245
measures you like. If the Mandos client
246
<emphasis>has</emphasis> an SSH server, the default
247
configuration (as generated by
248
<command>mandos-keygen</command> with the
249
<option>--password</option> option) is for the Mandos server
250
to use an <command>ssh-keyscan</command> command with strict
251
keychecking, which can not be faked. Alternatively, IPsec
252
could be used for the ping packets, making them secure.
224
measures you like. It could, for instance, be changed to an
225
SSH command with strict keychecking, which could not be faked.
226
Or IPsec could be used for the ping packets, making them
added
removed
intro.xml
