From 7243e04d4de6739af9e971200ad2ff6524039bd5 Mon Sep 17 00:00:00 2001 From: Thomas Glatthor Date: Wed, 3 Sep 2008 14:11:31 +0000 Subject: [PATCH] typo fix --- docs/manuals/en/concepts/dataencryption.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manuals/en/concepts/dataencryption.tex b/docs/manuals/en/concepts/dataencryption.tex index 34b050fe..e5943d26 100644 --- a/docs/manuals/en/concepts/dataencryption.tex +++ b/docs/manuals/en/concepts/dataencryption.tex @@ -19,7 +19,7 @@ do: possible for the director to restore new keys or a Bacula configuration file to the client, and thus force later backups to be made with a compromised key and/or with no encryption at all. You can avoid this by - not not changing the location of the keys in your Bacula File daemon + not changing the location of the keys in your Bacula File daemon configuration file, and not changing your File daemon keys. If you do change either one, you must ensure that no restore is done that restores the old configuration or the old keys. In general, the worst effect of @@ -122,7 +122,7 @@ You must: \begin{itemize} \item Concatenate the master private and public key into a single keypair file, ie: - cat master.key master.cert >master.keypair + cat master.key master.cert \gt master.keypair \item 2) Set the PKI Keypair statement in your bacula configuration file: -- 2.39.5