/mandos/trunk

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/trunk

« back to all changes in this revision

Viewing changes to intro.xml

  • Committer: teddy at bsnet
  • Date: 2011-12-25 00:40:09 UTC
  • Revision ID: teddy@fukt.bsnet.se-20111225004009-n5uimmac6h8djtv8
* plugin-runner.c (add_to_char_array): Added "nonnull" attribute.
  (add_argument): Added "nonnull" attribute on the "arg" argument.
  (add_environment): Added "nonnull" attribute on the "def" argument.
  (print_out_password, free_plugin): Added "nonnull" attribute.
  (main/parse_opt): Added "nonnull" attribute on the "state" argument.
* plugins.d/mandos-client.c (perror_plus): Bug fix; restore errno
                                           after fprintf().
* plugins.d/password-prompt.c (fprintf_plus): New.
 (conflict_detection/is_plymouth, main/parse_opt): Added "nonnull"
                                                   attribute.
 (conflict_detection/is_plymouth, conflict_detection, main): Bug fix;
                                                             Call
                                                             error_plus()
                                                             instead
                                                             of
                                                             error().
  (main/parse_opt): Added "nonnull" attribute on the "state" argument.
* plugins.d/plymouth.c (exec_and_wait): Added "nonnull" attribute on
                                        the "path" and "argv"
                                        arguments.
  (is_plymouth): Added "nonnull" attribute.

Show diffs side-by-side

added added

removed removed

Lines of Context:
intro.xml
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-07-20">
 
4
<!ENTITY TIMESTAMP "2011-10-03">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
31
31
    </authorgroup>
32
32
    <copyright>
33
33
      <year>2011</year>
34
 
      <year>2012</year>
35
 
      <year>2013</year>
36
 
      <year>2014</year>
37
 
      <year>2015</year>
38
34
      <holder>Teddy Hogeborn</holder>
39
35
      <holder>Björn Påhlsson</holder>
40
36
    </copyright>
200
196
      </para>
201
197
    </refsect2>
202
198
    
203
 
    <refsect2 id="sniff">
204
 
      <title>How about sniffing the network traffic and decrypting it
205
 
      later by physically grabbing the Mandos client and using its
206
 
      key?</title>
207
 
      <para>
208
 
        We only use <acronym>PFS</acronym> (Perfect Forward Security)
209
 
        key exchange algorithms in TLS, which protects against this.
210
 
      </para>
211
 
    </refsect2>
212
 
    
213
199
    <refsect2 id="physgrab">
214
200
      <title>Physically grabbing the Mandos server computer?</title>
215
201
      <para>
228
214
      </para>
229
215
    </refsect2>
230
216
    
231
 
    <refsect2 id="fakecheck">
232
 
      <title>Faking checker results?</title>
 
217
    <refsect2 id="fakeping">
 
218
      <title>Faking ping replies?</title>
233
219
      <para>
234
 
        If the Mandos client does not have an SSH server, the default
235
 
        is for the Mandos server to use
 
220
        The default for the server is to use
236
221
        <quote><literal>fping</literal></quote>, the replies to which
237
222
        could be faked to eliminate the timeout.  But this could
238
223
        easily be changed to any shell command, with any security
239
 
        measures you like.  If the Mandos client
240
 
        <emphasis>has</emphasis> an SSH server, the default
241
 
        configuration (as generated by
242
 
        <command>mandos-keygen</command> with the
243
 
        <option>--password</option> option) is for the Mandos server
244
 
        to use an <command>ssh-keyscan</command> command with strict
245
 
        keychecking, which can not be faked.  Alternatively, IPsec
246
 
        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
 
227
        secure.
247
228
      </para>
248
229
    </refsect2>
249
230
  </refsect1>