/mandos/trunk : revision 505.3.8

To get this branch, use:

bzr branch
http://bzr.recompile.se/loggerhead/mandos/trunk

« back to all changes in this revision

Viewing changes to mandos.xml

Committer: Teddy Hogeborn
Date: 2011-11-14 20:11:42 UTC
mto: (505.2.7 mandos-client-network-hooks)
mto: This revision was merged to the branch mainline in revision 525.
Revision ID: teddy@recompile.se-20111114201142-17zxc14jvonogwfx

* plugins.d/mandos-client.c (run_network_hooks): New.
  (main): Run run_network_hooks() with "stop" and "start" at
          appropriate places.  Don't lower privileges permanently
          prematurely.

Show diffs side-by-side

added added

removed removed

mandos.xml

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

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

<!ENTITY COMMANDNAME "mandos">

<!ENTITY TIMESTAMP "2011-11-26">

<!ENTITY TIMESTAMP "2011-10-03">

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

%common;

<sbr/>

<sbr/>

<arg><option>--no-restore</option></arg>

<sbr/>

100

<arg><option>--statedir

101

<replaceable>DIRECTORY</replaceable></option></arg>

102

</cmdsynopsis>

103

104

<command>&COMMANDNAME;</command>

280

275

<xi:include href="mandos-options.xml" xpointer="ipv6"/>

281

276

</listitem>

282

277

</varlistentry>

283

284

285

<term><option>--no-restore</option></term>

286

287

<xi:include href="mandos-options.xml" xpointer="restore"/>

288

</listitem>

289

</varlistentry>

290

291

292

<term><option>--statedir

293

<replaceable>DIRECTORY</replaceable></option></term>

294

295

<xi:include href="mandos-options.xml" xpointer="statedir"/>

296

</listitem>

297

</varlistentry>

298

278

</variablelist>

299

279

</refsect1>

300

280

407

387

<title>LOGGING</title>

408

388

<para>

409

389

The server will send log message with various severity levels to

410

<filename class="devicefile">/dev/log</filename>. With the

390

<filename>/dev/log</filename>. With the

411

391

<option>--debug</option> option, it will log even more messages,

412

392

and also show them on the console.

413

393

</para>

489

469

</listitem>

490

470

</varlistentry>

491

471

492

493

</varlistentry>

494

495

<term><filename

496

class="directory">/var/lib/mandos</filename></term>

497

498

<para>

499

Directory where persistent state will be saved. Change

500

this with the <option>--statedir</option> option. See

501

also the <option>--no-restore</option> option.

502

</para>

503

</listitem>

504

</varlistentry>

505

506

472

507

473

508

474

<para>

532

498

backtrace. This could be considered a feature.

533

499

</para>

534

500

<para>

501

Currently, if a client is disabled due to having timed out, the

502

server does not record this fact onto permanent storage. This

503

has some security implications, see <xref linkend="clients"/>.

504

</para>

505

<para>

535

506

There is no fine-grained control over logging and debug output.

536

507

</para>

537

508

<para>

538

509

Debug mode is conflated with running in the foreground.

539

510

</para>

540

511

<para>

512

The console log messages do not show a time stamp.

513

</para>

514

<para>

541

515

This server does not check the expire time of clients’ OpenPGP

542

516

keys.

543

517

</para>

556

530

557

531

<para>

558

532

Run the server in debug mode, read configuration files from

559

the <filename class="directory">~/mandos</filename> directory,

560

and use the Zeroconf service name <quote>Test</quote> to not

561

collide with any other official Mandos server on this host:

533

the <filename>~/mandos</filename> directory, and use the

534

Zeroconf service name <quote>Test</quote> to not collide with

535

any other official Mandos server on this host:

562

536

</para>

563

537

<para>

564

538

613

587

compromised if they are gone for too long.

614

588

</para>

615

589

<para>

590

If a client is compromised, its downtime should be duly noted

591

by the server which would therefore disable the client. But

592

if the server was ever restarted, it would re-read its client

593

list from its configuration file and again regard all clients

594

therein as enabled, and hence eligible to receive their

595

passwords. Therefore, be careful when restarting servers if

596

it is suspected that a client has, in fact, been compromised

597

by parties who may now be running a fake Mandos client with

598

the keys from the non-encrypted initial <acronym>RAM</acronym>

599

image of the client host. What should be done in that case

600

(if restarting the server program really is necessary) is to

601

stop the server program, edit the configuration file to omit

602

any suspect clients, and restart the server program.

603

</para>

604

<para>

616

605

For more details on client-side security, see

617

606

<citerefentry><refentrytitle>mandos-client</refentrytitle>

618

607

<manvolnum>8mandos</manvolnum></citerefentry>.

Older »