/mandos/trunk : revision 159

To get this branch, use:

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

« back to all changes in this revision

Viewing changes to plugins.d/password-request.xml

Committer: Teddy Hogeborn
Date: 2008-09-04 21:42:02 UTC
mfrom: (24.1.89 mandos)
Revision ID: teddy@fukt.bsnet.se-20080904214202-md7u3n1yqng8vz82

* Makefile (run-client): Do not depend on the key ring files.
  (keydir/secring.gpg, keydir/pubring.gpg): Removed.
  (confdir/mandos.conf): Install with proper mode.
  (confdir/clients.conf): - '' -

* mandos-keygen: Use a temporary directory with key ring files instead
                 of separate temporary key ring files.  Removed
                 "--no-random-seed" and "--no-permission-warning" from
                 all gpg invocations.

files added:
.bzrignore

COPYING

README

initramfs-tools-hook

initramfs-tools-hook-conf

initramfs-tools-script

legalnotice.xml

mandos-clients.conf.xml

mandos-keygen

mandos-keygen.xml

mandos-options.xml

mandos.conf

mandos.conf.xml

mandos.xml

overview.xml

plugin-runner.xml

plugins.d/password-prompt.xml

plugins.d/password-request.xml

plugins.d/usplash

files removed:
ca.pem

cert.pem

client-cert.pem

client-key.pem

crl.pem

key.pem

plugins.d/Makefile

files renamed:
mandos-clients.conf => clients.conf

server.py => mandos

plugbasedclient.c => plugin-runner.c

plugins.d/passprompt.c => plugins.d/password-prompt.c

plugins.d/mandosclient.c => plugins.d/password-request.c

files modified:
Makefile

TODO

Show diffs side-by-side

added added

removed removed

plugins.d/password-request.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 VERSION "1.0">

<!ENTITY COMMANDNAME "password-request">

<!ENTITY TIMESTAMP "2008-09-04">

<title>Mandos Manual</title>

<productname>Mandos</productname>

<productnumber>&VERSION;</productnumber>

<date>&TIMESTAMP;</date>

<firstname>Björn</firstname>

<surname>Påhlsson</surname>

<email>belorn@fukt.bsnet.se</email>

</address>

</author>

<firstname>Teddy</firstname>

<surname>Hogeborn</surname>

<email>teddy@fukt.bsnet.se</email>

</address>

</author>

</authorgroup>

<holder>Teddy Hogeborn</holder>

<holder>Björn Påhlsson</holder>

</copyright>

<xi:include href="../legalnotice.xml"/>

</refentryinfo>

<refentrytitle>&COMMANDNAME;</refentrytitle>

<manvolnum>8mandos</manvolnum>

</refmeta>

<refname><command>&COMMANDNAME;</command></refname>

Client for mandos

</refpurpose>

</refnamediv>

<command>&COMMANDNAME;</command>

<group>

<arg choice="plain"><option>--connect

<replaceable>ADDRESS</replaceable><literal>:</literal

><replaceable>PORT</replaceable></option></arg>

<arg choice="plain"><option>-c

<replaceable>ADDRESS</replaceable><literal>:</literal

><replaceable>PORT</replaceable></option></arg>

</group>

<sbr/>

<group>

<arg choice="plain"><option>--interface

<arg choice="plain"><option>-i

</group>

<sbr/>

<group>

<arg choice="plain"><option>--pubkey

<arg choice="plain"><option>-p

</group>

<sbr/>

<group>

<arg choice="plain"><option>--seckey

<arg choice="plain"><option>-s

</group>

<sbr/>

<arg>

<option>--priority <replaceable>STRING</replaceable></option>

</arg>

<sbr/>

<arg>

</arg>

<sbr/>

<arg>

<option>--debug</option>

</arg>

</cmdsynopsis>

<command>&COMMANDNAME;</command>

100

101

102

</group>

103

</cmdsynopsis>

104

105

<command>&COMMANDNAME;</command>

106

<arg choice="plain"><option>--usage</option></arg>

107

</cmdsynopsis>

108

109

<command>&COMMANDNAME;</command>

110

111

<arg choice="plain"><option>--version</option></arg>

112

113

</group>

114

</cmdsynopsis>

115

</refsynopsisdiv>

116

117

118

<title>DESCRIPTION</title>

119

<para>

120

<command>&COMMANDNAME;</command> is a client program that

121

communicates with <citerefentry><refentrytitle

122

>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>

123

to get a password. It uses IPv6 link-local addresses to get

124

network connectivity, Zeroconf to find servers, and TLS with an

125

OpenPGP key to ensure authenticity and confidentiality. It

126

keeps running, trying all servers on the network, until it

127

receives a satisfactory reply or a TERM signal is received.

128

</para>

129

<para>

130

This program is not meant to be run directly; it is really meant

131

to run as a plugin of the <application>Mandos</application>

132

<citerefentry><refentrytitle>plugin-runner</refentrytitle>

133

<manvolnum>8mandos</manvolnum></citerefentry>, which runs in the

134

initial <acronym>RAM</acronym> disk environment because it is

135

specified as a <quote>keyscript</quote> in the <citerefentry>

136

<refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>

137

</citerefentry> file.

138

</para>

139

</refsect1>

140

141

142

<title>PURPOSE</title>

143

<para>

144

The purpose of this is to enable <emphasis>remote and unattended

145

rebooting</emphasis> of client host computer with an

146

<emphasis>encrypted root file system</emphasis>. See <xref

147

linkend="overview"/> for details.

148

</para>

149

</refsect1>

150

151

152

<title>OPTIONS</title>

153

<para>

154

This program is commonly not invoked from the command line; it

155

is normally started by the <application>Mandos</application>

156

plugin runner, see <citerefentry><refentrytitle

157

>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>

158

</citerefentry>. Any command line options this program accepts

159

are therefore normally provided by the plugin runner, and not

160

directly.

161

</para>

162

163

164

165

<term><option>--connect=<replaceable

166

>ADDRESS</replaceable><literal>:</literal><replaceable

167

>PORT</replaceable></option></term>

168

<term><option>-c

169

<replaceable>ADDRESS</replaceable><literal>:</literal

170

><replaceable>PORT</replaceable></option></term>

171

172

<para>

173

Do not use Zeroconf to locate servers. Connect directly

174

to only one specified <application>Mandos</application>

175

server. Note that an IPv6 address has colon characters in

176

it, so the <emphasis>last</emphasis> colon character is

177

assumed to separate the address from the port number.

178

</para>

179

<para>

180

This option is normally only useful for testing and

181

debugging.

182

</para>

183

</listitem>

184

</varlistentry>

185

186

187

<term><option>--interface=

188

189

<term><option>-i

190

191

192

<para>

193

Network interface that will be brought up and scanned for

194

Mandos servers to connect to. The default it

195

<quote><literal>eth0</literal></quote>.

196

</para>

197

<para>

198

If the <option>--connect</option> option is used, this

199

specifies the interface to use to connect to the address

200

given.

201

</para>

202

</listitem>

203

</varlistentry>

204

205

206

<term><option>--pubkey=<replaceable

207

>FILE</replaceable></option></term>

208

<term><option>-p

209

210

211

<para>

212

OpenPGP public key file name. The default name is

213

<quote><filename>/conf/conf.d/mandos/pubkey.txt</filename

214

></quote>.

215

</para>

216

</listitem>

217

</varlistentry>

218

219

220

<term><option>--seckey=<replaceable

221

>FILE</replaceable></option></term>

222

<term><option>-s

223

224

225

<para>

226

OpenPGP secret key file name. The default name is

227

<quote><filename>/conf/conf.d/mandos/seckey.txt</filename

228

></quote>.

229

</para>

230

</listitem>

231

</varlistentry>

232

233

234

<term><option>--priority=<replaceable

235

>STRING</replaceable></option></term>

236

237

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

238

xpointer="priority"/>

239

</listitem>

240

</varlistentry>

241

242

243

<term><option>--dh-bits=<replaceable

244

>BITS</replaceable></option></term>

245

246

<para>

247

Sets the number of bits to use for the prime number in the

248

TLS Diffie-Hellman key exchange. Default is 1024.

249

</para>

250

</listitem>

251

</varlistentry>

252

253

254

<term><option>--debug</option></term>

255

256

<para>

257

Enable debug mode. This will enable a lot of output to

258

standard error about what the program is doing. The

259

program will still perform all other functions normally.

260

</para>

261

<para>

262

It will also enable debug mode in the Avahi and GnuTLS

263

libraries, making them print large amounts of debugging

264

output.

265

</para>

266

</listitem>

267

</varlistentry>

268

269

270

271

272

273

<para>

274

Gives a help message about options and their meanings.

275

</para>

276

</listitem>

277

</varlistentry>

278

279

280

<term><option>--usage</option></term>

281

282

<para>

283

Gives a short usage message.

284

</para>

285

</listitem>

286

</varlistentry>

287

288

289

<term><option>--version</option></term>

290

291

292

<para>

293

Prints the program version.

294

</para>

295

</listitem>

296

</varlistentry>

297

</variablelist>

298

</refsect1>

299

300

301

<title>OVERVIEW</title>

302

<xi:include href="../overview.xml"/>

303

<para>

304

This program is the client part. It is a plugin started by

305

<citerefentry><refentrytitle>plugin-runner</refentrytitle>

306

<manvolnum>8mandos</manvolnum></citerefentry> which will run in

307

an initial <acronym>RAM</acronym> disk environment.

308

</para>

309

<para>

310

This program could, theoretically, be used as a keyscript in

311

<filename>/etc/crypttab</filename>, but it would then be

312

impossible to enter a password for the encrypted root disk at

313

the console, since this program does not read from the console

314

at all. This is why a separate plugin (<citerefentry>

315

<refentrytitle>password-prompt</refentrytitle>

316

<manvolnum>8mandos</manvolnum></citerefentry>) does that, which

317

will be run in parallel to this one by the plugin runner.

318

</para>

319

</refsect1>

320

321

322

<title>EXIT STATUS</title>

323

<para>

324

This program will exit with a successful (zero) exit status if a

325

server could be found and the password received from it could be

326

successfully decrypted and output on standard output. The

327

program will exit with a non-zero exit status only if a critical

328

error occurs. Otherwise, it will forever connect to new

329

<application>Mandos</application> servers as they appear, trying

330

to get a decryptable password.

331

</para>

332

</refsect1>

333

334

335

<title>ENVIRONMENT</title>

336

<para>

337

This program does not use any environment variables, not even

338

the ones provided by <citerefentry><refentrytitle

339

>cryptsetup</refentrytitle><manvolnum>8</manvolnum>

340

</citerefentry>.

341

</para>

342

</refsect1>

343

344

345

<title>FILES</title>

346

347

348

<term><filename>/conf/conf.d/mandos/pubkey.txt</filename

349

></term>

350

<term><filename>/conf/conf.d/mandos/seckey.txt</filename

351

></term>

352

353

<para>

354

OpenPGP public and private key files, in <quote>ASCII

355

Armor</quote> format. These are the default file names,

356

they can be changed with the <option>--pubkey</option> and

357

<option>--seckey</option> options.

358

</para>

359

</listitem>

360

</varlistentry>

361

</variablelist>

362

</refsect1>

363

364

365

366

367

368

369

370

371

<title>EXAMPLE</title>

372

<para>

373

Note that normally, command line options will not be given

374

directly, but via options for the Mandos <citerefentry

375

><refentrytitle>plugin-runner</refentrytitle>

376

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

377

</para>

378

379

<para>

380

Normal invocation needs no options, if the network interface

381

is <quote>eth0</quote>:

382

</para>

383

<para>

384

<userinput>&COMMANDNAME;</userinput>

385

</para>

386

</informalexample>

387

388

<para>

389

Search for Mandos servers (and connect to them) using another

390

interface:

391

</para>

392

<para>

393

394

<userinput>&COMMANDNAME; --interface eth1</userinput>

395

</para>

396

</informalexample>

397

398

<para>

399

Run in debug mode, and use a custom key:

400

</para>

401

<para>

402

403

404

<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>

405

406

</para>

407

</informalexample>

408

409

<para>

410

Run in debug mode, with a custom key, and do not use Zeroconf

411

to locate a server; connect directly to the IPv6 address

412

<quote><systemitem class="ipaddress"

413

>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,

414

port 4711, using interface eth2:

415

</para>

416

<para>

417

418

419

<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>

420

421

</para>

422

</informalexample>

423

</refsect1>

424

425

426

<title>SECURITY</title>

427

<para>

428

This program is set-uid to root, but will switch back to the

429

original (and presumably non-privileged) user and group after

430

bringing up the network interface.

431

</para>

432

<para>

433

To use this program for its intended purpose (see <xref

434

linkend="purpose"/>), the password for the root file system will

435

have to be given out to be stored in a server computer, after

436

having been encrypted using an OpenPGP key. This encrypted data

437

which will be stored in a server can only be decrypted by the

438

OpenPGP key, and the data will only be given out to those

439

clients who can prove they actually have that key. This key,

440

however, is stored unencrypted on the client side in its initial

441

<acronym>RAM</acronym> disk image file system. This is normally

442

readable by all, but this is normally fixed during installation

443

of this program; file permissions are set so that no-one is able

444

to read that file.

445

</para>

446

<para>

447

The only remaining weak point is that someone with physical

448

access to the client hard drive might turn off the client

449

computer, read the OpenPGP keys directly from the hard drive,

450

and communicate with the server. The defense against this is

451

that the server is supposed to notice the client disappearing

452

and will stop giving out the encrypted data. Therefore, it is

453

important to set the timeout and checker interval values tightly

454

on the server. See <citerefentry><refentrytitle

455

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

456

</para>

457

<para>

458

It will also help if the checker program on the server is

459

configured to request something from the client which can not be

460

spoofed by someone else on the network, unlike unencrypted

461

<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.

462

</para>

463

<para>

464

<emphasis>Note</emphasis>: This makes it completely insecure to

465

have <application >Mandos</application> clients which dual-boot

466

to another operating system which is <emphasis>not</emphasis>

467

trusted to keep the initial <acronym>RAM</acronym> disk image

468

confidential.

469

</para>

470

</refsect1>

471

472

473

474

<para>

475

<citerefentry><refentrytitle>cryptsetup</refentrytitle>

476

<manvolnum>8</manvolnum></citerefentry>,

477

<citerefentry><refentrytitle>crypttab</refentrytitle>

478

<manvolnum>5</manvolnum></citerefentry>,

479

<citerefentry><refentrytitle>mandos</refentrytitle>

480

<manvolnum>8</manvolnum></citerefentry>,

481

<citerefentry><refentrytitle>password-prompt</refentrytitle>

482

<manvolnum>8mandos</manvolnum></citerefentry>,

483

<citerefentry><refentrytitle>plugin-runner</refentrytitle>

484

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

485

</para>

486

487

488

<term>

489

<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>

490

</term>

491

492

<para>

493

Zeroconf is the network protocol standard used for finding

494

Mandos servers on the local network.

495

</para>

496

</listitem>

497

</varlistentry>

498

499

<term>

500

<ulink url="http://www.avahi.org/">Avahi</ulink>

501

</term>

502

503

<para>

504

Avahi is the library this program calls to find Zeroconf

505

services.

506

</para>

507

</listitem>

508

</varlistentry>

509

510

<term>

511

<ulink url="http://www.gnu.org/software/gnutls/"

512

>GnuTLS</ulink>

513

</term>

514

515

<para>

516

GnuTLS is the library this client uses to implement TLS for

517

communicating securely with the server, and at the same time

518

send the public OpenPGP key to the server.

519

</para>

520

</listitem>

521

</varlistentry>

522

523

<term>

524

<ulink url="http://www.gnupg.org/related_software/gpgme/"

525

>GPGME</ulink>

526

</term>

527

528

<para>

529

GPGME is the library used to decrypt the OpenPGP data sent

530

by the server.

531

</para>

532

</listitem>

533

</varlistentry>

534

535

<term>

536

RFC 4291: <citetitle>IP Version 6 Addressing

537

Architecture</citetitle>

538

</term>

539

540

541

542

<term>Section 2.2: <citetitle>Text Representation of

543

Addresses</citetitle></term>

544

545

</varlistentry>

546

547

<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6

548

Address</citetitle></term>

549

550

</varlistentry>

551

552

<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast

553

Addresses</citetitle></term>

554

555

<para>

556

This client uses IPv6 link-local addresses, which are

557

immediately usable since a link-local addresses is

558

automatically assigned to a network interfaces when it

559

is brought up.

560

</para>

561

</listitem>

562

</varlistentry>

563

</variablelist>

564

</listitem>

565

</varlistentry>

566

567

<term>

568

RFC 4346: <citetitle>The Transport Layer Security (TLS)

569

Protocol Version 1.1</citetitle>

570

</term>

571

572

<para>

573

TLS 1.1 is the protocol implemented by GnuTLS.

574

</para>

575

</listitem>

576

</varlistentry>

577

578

<term>

579

RFC 4880: <citetitle>OpenPGP Message Format</citetitle>

580

</term>

581

582

<para>

583

The data received from the server is binary encrypted

584

OpenPGP data.

585

</para>

586

</listitem>

587

</varlistentry>

588

589

<term>

590

RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer

591

Security</citetitle>

592

</term>

593

594

<para>

595

This is implemented by GnuTLS and used by this program so

596

that OpenPGP keys can be used.

597

</para>

598

</listitem>

599

</varlistentry>

600

</variablelist>

601

</refsect1>

602

603

</refentry>

604

605

606

607

608

Older »