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 "2020-09-16">
4
<!ENTITY TIMESTAMP "2017-02-23">
5
5
<!ENTITY % common SYSTEM "common.ent">
69
66
The computers run a small client program in the initial RAM disk
70
67
environment which will communicate with a server over a network.
71
68
All network communication is encrypted using TLS. The clients
72
are identified by the server using a TLS public key; each client
69
are identified by the server using an OpenPGP key; each client
73
70
has one unique to it. The server sends the clients an encrypted
74
71
password. The encrypted password is decrypted by the clients
75
using a separate OpenPGP key, and the password is then used to
72
using the same OpenPGP key, and the password is then used to
76
73
unlock the root file system, whereupon the computers can
77
74
continue booting normally.
134
131
So, at boot time, the Mandos client will ask for its encrypted
135
data over the network, decrypt the data to get the password, use
136
the password to decrypt the root file system, and the client can
137
then continue booting.
132
data over the network, decrypt it to get the password, use it to
133
decrypt the root file, and continue booting.
140
136
Now, of course the initial RAM disk image is not on the
146
142
long, and will no longer give out the encrypted key. The timing
147
143
here is the only real weak point, and the method, frequency and
148
144
timeout of the server’s checking can be adjusted to any desired
152
148
(The encrypted keys on the Mandos server is on its normal file
204
200
No. The server only gives out the passwords to clients which
205
201
have <emphasis>in the TLS handshake</emphasis> proven that
206
they do indeed hold the private key corresponding to that
202
they do indeed hold the OpenPGP private key corresponding to
385
381
plugin requirements.
389
<refsect1 id="systemd">
390
<title>SYSTEMD</title>
392
More advanced startup systems like <citerefentry><refentrytitle
393
>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
394
already have their own plugin-like mechanisms for allowing
395
multiple agents to independently retrieve a password and deliver
396
it to the subsystem requesting a password to unlock the root
397
file system. On these systems, it would make no sense to run
398
<citerefentry><refentrytitle>plugin-runner</refentrytitle
399
><manvolnum>8mandos</manvolnum></citerefentry>, the plugins of
400
which would largely duplicate the work of (and conflict with)
401
the existing systems prompting for passwords.
404
As for <citerefentry><refentrytitle>systemd</refentrytitle
405
><manvolnum>1</manvolnum></citerefentry> in particular, it has
407
url="https://systemd.io/PASSWORD_AGENTS/">Password
408
Agents</ulink> system. Mandos uses this via its
409
<citerefentry><refentrytitle>password-agent</refentrytitle
410
><manvolnum>8mandos</manvolnum></citerefentry> program, which is
411
run instead of <citerefentry><refentrytitle
412
>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum
413
></citerefentry> when <citerefentry><refentrytitle
414
>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
415
is used during system startup.
418
385
<refsect1 id="bugs">
419
386
<title>BUGS</title>
420
387
<xi:include href="bugs.xml"/>
435
402
<manvolnum>8</manvolnum></citerefentry>,
436
403
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
437
404
<manvolnum>8mandos</manvolnum></citerefentry>,
438
<citerefentry><refentrytitle>password-agent</refentrytitle>
439
<manvolnum>8mandos</manvolnum></citerefentry>,
440
405
<citerefentry><refentrytitle>mandos-client</refentrytitle>
441
406
<manvolnum>8mandos</manvolnum></citerefentry>,
442
407
<citerefentry><refentrytitle>password-prompt</refentrytitle>
added
removed
intro.xml
