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 "2011-10-03">
4
<!ENTITY TIMESTAMP "2019-03-30">
5
5
<!ENTITY % common SYSTEM "common.ent">
60
68
The computers run a small client program in the initial RAM disk
61
69
environment which will communicate with a server over a network.
62
70
All network communication is encrypted using TLS. The clients
63
are identified by the server using an OpenPGP key; each client
71
are identified by the server using a TLS public key; each client
64
72
has one unique to it. The server sends the clients an encrypted
65
73
password. The encrypted password is decrypted by the clients
66
using the same OpenPGP key, and the password is then used to
74
using a separate OpenPGP key, and the password is then used to
67
75
unlock the root file system, whereupon the computers can
68
76
continue booting normally.
72
80
<refsect1 id="introduction">
73
81
<title>INTRODUCTION</title>
83
<!-- This paragraph is a combination and paraphrase of two
84
quotes from the 1995 movie “The Usual Suspects”. -->
75
85
You know how it is. You’ve heard of it happening. The Man
76
86
comes and takes away your servers, your friends’ servers, the
77
87
servers of everybody in the same hosting facility. The servers
134
144
long, and will no longer give out the encrypted key. The timing
135
145
here is the only real weak point, and the method, frequency and
136
146
timeout of the server’s checking can be adjusted to any desired
140
150
(The encrypted keys on the Mandos server is on its normal file
192
202
No. The server only gives out the passwords to clients which
193
203
have <emphasis>in the TLS handshake</emphasis> proven that
194
they do indeed hold the OpenPGP private key corresponding to
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.
217
<refsect2 id="fakeping">
218
<title>Faking ping replies?</title>
237
<refsect2 id="fakecheck">
238
<title>Faking checker results?</title>
220
The default for the server is to use
240
If the Mandos client does not have an SSH server, the default
241
is for the Mandos server to use
221
242
<quote><literal>fping</literal></quote>, the replies to which
222
243
could be faked to eliminate the timeout. But this could
223
244
easily be changed to any shell command, with any security
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
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.
added
removed
intro.xml
