/mandos/trunk : revision 961

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 Hogeborn
Date: 2018-10-14 14:11:15 UTC
Revision ID: teddy@recompile.se-20181014141115-1oilce79snz1ackb

Depend on either old cryptsetup or new cryptsetup-initramfs

* debian/control (Package: mandos-client/Depends): Change "cryptsetup"
to "cryptsetup (<< 2:2.0.3-1) | cryptsetup-initramfs".

Show diffs side-by-side

added added

removed removed

intro.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"

"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [

<!ENTITY TIMESTAMP "2019-02-09">

<!ENTITY TIMESTAMP "2018-02-08">

<!ENTITY % common SYSTEM "common.ent">

%common;

The computers run a small client program in the initial RAM disk

environment which will communicate with a server over a network.

All network communication is encrypted using TLS. The clients

are identified by the server using a TLS public key; each client

are identified by the server using an OpenPGP key; each client

has one unique to it. The server sends the clients an encrypted

password. The encrypted password is decrypted by the clients

using a separate OpenPGP key, and the password is then used to

using the same OpenPGP key, and the password is then used to

unlock the root file system, whereupon the computers can

continue booting normally.

</para>

200

<para>

201

No. The server only gives out the passwords to clients which

202

have <emphasis>in the TLS handshake</emphasis> proven that

203

they do indeed hold the private key corresponding to that

204

client.

203

they do indeed hold the OpenPGP private key corresponding to

204

that client.

205

</para>

206

</refsect2>

207

Older »