From 549614037774f391166e5df67f8bd1e57cce46da Mon Sep 17 00:00:00 2001 From: Alexander Wirt Date: Sun, 17 Jul 2011 10:00:16 +0200 Subject: [PATCH] Add header, reorder headlines --- README.asciidoc | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/README.asciidoc b/README.asciidoc index c546a2d..3668e4b 100644 --- a/README.asciidoc +++ b/README.asciidoc @@ -1,5 +1,11 @@ +pwstore documentation +===================== +Peter Palfrader, Alexander Wirt +v0.1 July 2011 + + introduction -============ +------------ The pws tool allows you to store passwords (or anything else, really) in a set of encrypted files. Each file can be encrypted to a different set @@ -7,7 +13,8 @@ of users. pws helps you with the bookkeeping of which keys to encrypt each file to and provides a convinient wrapper to edit protected files. initialization -============== +-------------- + First you need a file where your users and group are defined in. This file is named .users. Lines consist of assignments of the form = @@ -56,14 +63,14 @@ might have. A patch to remove this limitation would be nice. adding a new file -================= +----------------- ----------------------------- # pws ed -n file ----------------------------- editing files -============= +------------- Every file needs a header like: @@ -74,7 +81,7 @@ access: @all You can edit the encrypted file with the pws tool: +pwd ed file+. updating the keyring -==================== +-------------------- If available as .keyring pws instructs GnuPG to use this keyring in addition to the user's default keyrings. This allows sharing of the -- 2.39.5