summaryrefslogtreecommitdiff
path: root/pwgrep.buetow.org/content/Tutorials.sub
diff options
context:
space:
mode:
authorPaul Buetow (mars.fritz.box) <paul@buetow.org>2013-09-28 18:02:25 +0200
committerPaul Buetow (mars.fritz.box) <paul@buetow.org>2013-09-28 18:02:25 +0200
commit2bfe5014a3ec0c2dc04fc3a72420ca86f5fac524 (patch)
tree7f28e95ae7ac97f435eba0418e999db474e6a15a /pwgrep.buetow.org/content/Tutorials.sub
parent714164e679851987512435ed9b88f094c822e9f3 (diff)
reformat XML
Diffstat (limited to 'pwgrep.buetow.org/content/Tutorials.sub')
-rw-r--r--pwgrep.buetow.org/content/Tutorials.sub/10.Passwords.xml47
-rw-r--r--pwgrep.buetow.org/content/Tutorials.sub/20.Files.xml31
-rw-r--r--pwgrep.buetow.org/content/Tutorials.sub/home.xml2
3 files changed, 39 insertions, 41 deletions
diff --git a/pwgrep.buetow.org/content/Tutorials.sub/10.Passwords.xml b/pwgrep.buetow.org/content/Tutorials.sub/10.Passwords.xml
index 456b4f7..c5fe33e 100644
--- a/pwgrep.buetow.org/content/Tutorials.sub/10.Passwords.xml
+++ b/pwgrep.buetow.org/content/Tutorials.sub/10.Passwords.xml
@@ -1,10 +1,10 @@
-<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
+<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<content>
- <pagetitle>Tutorial for storing passwords</pagetitle>
- <text>First check out pwgrep from git and edit the configuration parameters in its header. Also setup a versioning repository (e.g. svn) for your password database storage (preferable using some encryption for checkout/update operations such as SSL or SSH). Afterwards you may go on with the usage of pwgrep itself:</text>
- <text>Please note that the current version of pwgrep is configured to work with git. The rest of this tutorial however should work as with svn.</text>
- <text>The database file is divided in several records. Each record begins with its name followed by several lines holding all the secret informations. The (actually very simple) format of the database file is as follows:</text>
- <code>
+ <pagetitle>Tutorial for storing passwords</pagetitle>
+ <text>First check out pwgrep from git and edit the configuration parameters in its header. Also setup a versioning repository (e.g. svn) for your password database storage (preferable using some encryption for checkout/update operations such as SSL or SSH). Afterwards you may go on with the usage of pwgrep itself:</text>
+ <text>Please note that the current version of pwgrep is configured to work with git. The rest of this tutorial however should work as with svn.</text>
+ <text>The database file is divided in several records. Each record begins with its name followed by several lines holding all the secret informations. The (actually very simple) format of the database file is as follows:</text>
+ <code>
some record name here
after a tabulator some secret informations
more secret informations
@@ -20,22 +20,21 @@ secret stuff
.
.
</code>
- <text>The database is not stored in plain text. It is encrypted using GnuPG (database.gpg).</text>
- <text>I can only search for the record names of a database file. For example if I want to see my secret username and password which is stored in the database.gpg file it will look like this:</text>
- <cimg href="?document=images/1.png" />
- <text>After entering the password of my secret GnuPG key I will receive the informations requested:</text>
- <cimg href="?document=images/2.png" />
- <text>pwgrep will print out automatically all records matching my search string. Not only the first one it finds.</text>
- <text>I can use pwedit for the case I want to add something to the database or just to edit/delete something of the current database:</text>
- <cimg href="?document=images/3.png" />
- <cimg href="?document=images/4.png" />
- <text>After editing, pwgrep will automatically wipe all temporally files securely and it will commit the new version into the versioning system (In this case subversion is being used. But others can be configured as well). pwgrep is using Vim (with swapping and backuping disabled) in order to edit the database file. If you want to use a different editor, you should make sure NOT to produce temporally files. If you produce temporally files, at least they should get wiped securely from the hard disk.</text>
- <cimg href="?document=images/5.png" />
- <cimg href="?document=images/6.png" />
- <text>If you want to look up your secret ebay stuff, just search for it with</text>
- <code> ~/svn/pwgrep$ pwgrep ebay</code>
- <text>Since pwgrep v0.5 it's possible to specify the offline option, which causes pwgrep not use versioning at all (usable if there is no connection to the subversion or CVS server available):</text>
- <code> ~/svn/pwgrep$ pwgrep -o ebay</code>
- <text>All commands support the -o option</text>
+ <text>The database is not stored in plain text. It is encrypted using GnuPG (database.gpg).</text>
+ <text>I can only search for the record names of a database file. For example if I want to see my secret username and password which is stored in the database.gpg file it will look like this:</text>
+ <cimg href="?document=images/1.png"/>
+ <text>After entering the password of my secret GnuPG key I will receive the informations requested:</text>
+ <cimg href="?document=images/2.png"/>
+ <text>pwgrep will print out automatically all records matching my search string. Not only the first one it finds.</text>
+ <text>I can use pwedit for the case I want to add something to the database or just to edit/delete something of the current database:</text>
+ <cimg href="?document=images/3.png"/>
+ <cimg href="?document=images/4.png"/>
+ <text>After editing, pwgrep will automatically wipe all temporally files securely and it will commit the new version into the versioning system (In this case subversion is being used. But others can be configured as well). pwgrep is using Vim (with swapping and backuping disabled) in order to edit the database file. If you want to use a different editor, you should make sure NOT to produce temporally files. If you produce temporally files, at least they should get wiped securely from the hard disk.</text>
+ <cimg href="?document=images/5.png"/>
+ <cimg href="?document=images/6.png"/>
+ <text>If you want to look up your secret ebay stuff, just search for it with</text>
+ <code> ~/svn/pwgrep$ pwgrep ebay</code>
+ <text>Since pwgrep v0.5 it's possible to specify the offline option, which causes pwgrep not use versioning at all (usable if there is no connection to the subversion or CVS server available):</text>
+ <code> ~/svn/pwgrep$ pwgrep -o ebay</code>
+ <text>All commands support the -o option</text>
</content>
-
diff --git a/pwgrep.buetow.org/content/Tutorials.sub/20.Files.xml b/pwgrep.buetow.org/content/Tutorials.sub/20.Files.xml
index 8d8b1b9..06f443f 100644
--- a/pwgrep.buetow.org/content/Tutorials.sub/20.Files.xml
+++ b/pwgrep.buetow.org/content/Tutorials.sub/20.Files.xml
@@ -1,18 +1,17 @@
-<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
+<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<content>
- <pagetitle>Tutorial for storing files</pagetitle>
- <text>Please read the "tutorial for storing passwords" first. Afterwards you may go on with this tutorial. This tutorial expects you to have understood the basics of pwgrep.</text>
- <text>Besides of storing passwords into a single file, pwgrep can also be used for storing a collection of files, which is very usefull for storing certificate files etc. Like passwords, all files stored within pwgrep are encrypted using GPG. The command pwfls will list all files currently stored in your database:</text>
- <cimg href="?document=images/7.png" />
- <text>pwfadd adds a specific file to the database:</text>
- <cimg href="?document=images/8.png" />
- <cimg href="?document=images/9.png" />
- <text>pwfls will show you that it has been added successfully:</text>
- <cimg href="?document=images/10.png" />
- <text>In order to decrypt a specific stored file you have to use pwfcat:</text>
- <cimg href="?document=images/11.png" />
- <text>File deletion can be accomplished using pwfdel:</text>
- <cimg href="?document=images/12.png" />
- <text>In general you can decrypt/store/encrypt any specific file format (as well as binary files).</text>
+ <pagetitle>Tutorial for storing files</pagetitle>
+ <text>Please read the "tutorial for storing passwords" first. Afterwards you may go on with this tutorial. This tutorial expects you to have understood the basics of pwgrep.</text>
+ <text>Besides of storing passwords into a single file, pwgrep can also be used for storing a collection of files, which is very usefull for storing certificate files etc. Like passwords, all files stored within pwgrep are encrypted using GPG. The command pwfls will list all files currently stored in your database:</text>
+ <cimg href="?document=images/7.png"/>
+ <text>pwfadd adds a specific file to the database:</text>
+ <cimg href="?document=images/8.png"/>
+ <cimg href="?document=images/9.png"/>
+ <text>pwfls will show you that it has been added successfully:</text>
+ <cimg href="?document=images/10.png"/>
+ <text>In order to decrypt a specific stored file you have to use pwfcat:</text>
+ <cimg href="?document=images/11.png"/>
+ <text>File deletion can be accomplished using pwfdel:</text>
+ <cimg href="?document=images/12.png"/>
+ <text>In general you can decrypt/store/encrypt any specific file format (as well as binary files).</text>
</content>
-
diff --git a/pwgrep.buetow.org/content/Tutorials.sub/home.xml b/pwgrep.buetow.org/content/Tutorials.sub/home.xml
index 3ce6ed6..5b89810 100644
--- a/pwgrep.buetow.org/content/Tutorials.sub/home.xml
+++ b/pwgrep.buetow.org/content/Tutorials.sub/home.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?>
+<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<content>
<pagetitle>Tutorials...</pagetitle>
<text>...for using pwgrep.</text>