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 "2015-03-08">
4
<!ENTITY TIMESTAMP "2011-10-03">
5
5
<!ENTITY % common SYSTEM "common.ent">
200
<refsect2 id="sniff">
201
<title>How about sniffing the network traffic and decrypting it
202
later by physically grabbing the Mandos client and using its
205
We only use <acronym>PFS</acronym> (Perfect Forward Security)
206
key exchange algorithms in TLS, which protects against this.
210
199
<refsect2 id="physgrab">
211
200
<title>Physically grabbing the Mandos server computer?</title>
228
<refsect2 id="fakecheck">
229
<title>Faking checker results?</title>
217
<refsect2 id="fakeping">
218
<title>Faking ping replies?</title>
231
If the Mandos client does not have an SSH server, the default
232
is for the Mandos server to use
220
The default for the server is to use
233
221
<quote><literal>fping</literal></quote>, the replies to which
234
222
could be faked to eliminate the timeout. But this could
235
223
easily be changed to any shell command, with any security
236
measures you like. If the Mandos client
237
<emphasis>has</emphasis> an SSH server, the default
238
configuration (as generated by
239
<command>mandos-keygen</command> with the
240
<option>--password</option> option) is for the Mandos server
241
to use an <command>ssh-keyscan</command> command with strict
242
keychecking, which can not be faked. Alternatively, IPsec
243
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
