|
From: <di...@us...> - 2007-02-02 00:53:11
|
Revision: 360
http://safekeep.svn.sourceforge.net/safekeep/?rev=360&view=rev
Author: dimi
Date: 2007-02-01 16:53:10 -0800 (Thu, 01 Feb 2007)
Log Message:
-----------
Add documentation about keys deployment
Modified Paths:
--------------
safekeep/trunk/doc/safekeep.txt
Modified: safekeep/trunk/doc/safekeep.txt
===================================================================
--- safekeep/trunk/doc/safekeep.txt 2007-02-02 00:43:23 UTC (rev 359)
+++ safekeep/trunk/doc/safekeep.txt 2007-02-02 00:53:10 UTC (rev 360)
@@ -182,6 +182,22 @@
`my_workstation.conf`, the client ID becomes `my_workstation`. For more
information on this topic, see safekeep.conf(5).
+KEY DEPLOYMENT
+--------------
+The `safekeep(1)` server needs to access the clients in order to conduct
+the backup. To that end, it establishes two ssh(1) pipes: one for control,
+and one for data. To simplify the deployment of the keys, `safekeep(1)`
+has a key deploy mode.
+
+When deploying keys using the built-in key management functionality,
+`safekeep(1)` needs to be invoked as the user under which it will function
+as a server. By default, that user is 'safekeep'. For extra security,
+you can not login into that account, so you have to invoke `safekeep(1)`
+as follows:
+------------------------------------------------------------------------
+ # sudo -H -u safekeep safekeep --keys --deploy
+------------------------------------------------------------------------
+
SEE ALSO
--------
rdiff-backup(1), safekeep.conf(5)
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|