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 "2016-03-22">
5
5
<!ENTITY % common SYSTEM "common.ent">
204
<refsect2 id="sniff">
205
<title>How about sniffing the network traffic and decrypting it
206
later by physically grabbing the Mandos client and using its
209
We only use <acronym>PFS</acronym> (Perfect Forward Security)
210
key exchange algorithms in TLS, which protects against this.
199
214
<refsect2 id="physgrab">
200
215
<title>Physically grabbing the Mandos server computer?</title>
217
<refsect2 id="fakeping">
218
<title>Faking ping replies?</title>
232
<refsect2 id="fakecheck">
233
<title>Faking checker results?</title>
220
The default for the server is to use
235
If the Mandos client does not have an SSH server, the default
236
is for the Mandos server to use
221
237
<quote><literal>fping</literal></quote>, the replies to which
222
238
could be faked to eliminate the timeout. But this could
223
239
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
240
measures you like. If the Mandos client
241
<emphasis>has</emphasis> an SSH server, the default
242
configuration (as generated by
243
<command>mandos-keygen</command> with the
244
<option>--password</option> option) is for the Mandos server
245
to use an <command>ssh-keyscan</command> command with strict
246
keychecking, which can not be faked. Alternatively, IPsec
247
could be used for the ping packets, making them secure.
added
removed
intro.xml
