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 "2016-03-22">
4
<!ENTITY TIMESTAMP "2012-01-01">
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.
214
200
<refsect2 id="physgrab">
215
201
<title>Physically grabbing the Mandos server computer?</title>
232
<refsect2 id="fakecheck">
233
<title>Faking checker results?</title>
218
<refsect2 id="fakeping">
219
<title>Faking ping replies?</title>
235
If the Mandos client does not have an SSH server, the default
236
is for the Mandos server to use
221
The default for the server is to use
237
222
<quote><literal>fping</literal></quote>, the replies to which
238
223
could be faked to eliminate the timeout. But this could
239
224
easily be changed to any shell command, with any security
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.
225
measures you like. It could, for instance, be changed to an
226
SSH command with strict keychecking, which could not be faked.
227
Or IPsec could be used for the ping packets, making them
added
removed
intro.xml
