Updates

[bacula/docs] / docs / manual / dataencryption.tex

diff --git a/docs/manual/dataencryption.tex b/docs/manual/dataencryption.tex
index 75ad43b293b096f798cee0be9b93fc71a6be9543..07e89c01cb3ba784d5e7cb2b0140791382a52696 100644 (file)
--- a/docs/manual/dataencryption.tex
+++ b/docs/manual/dataencryption.tex
@@ -16,14 +16,15 @@ contents.
 It is very important to specify what this implementation does NOT
 do:
 \begin{itemize}
-\item  There is still one major gotcha, namely, it's 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 backing
-  up your encryption keys using Bacula, and not changing the location
-  of the keys in your Bacula File daemon configuration file.  However,
-  please be sure your File daemon keys securely backed up preferably
-  off-site.
+\item There is one important restore problem to be aware of, namely, it's
+  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
+  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
+  this will be that you can no longer connect the File daemon.
 
 \item The implementation does not encrypt file metadata such as file path
   names, permissions, and ownership. Extended attributes are also currently
@@ -54,6 +55,15 @@ home with the owner of the machine.
 NOTE!!! If you lose your encryption keys, backups will be unrecoverable.
 {\bf ALWAYS} store a copy of your master keys in a secure, off-site location.
 
+The basic algorithm used for each backup session (Job) is:
+\begin{enumerate}
+\item The File daemon generates a session key.
+\item The FD encrypts that session key via PKE for all recipients (the file  
+daemon, any master keys).
+\item The FD uses that session key to perform symmetric encryption on the data.
+\end{enumerate}
+
+
 \subsection*{Building Bacula with Encryption Support}
 \index[general]{Building Bacula with Encryption Support}
 \addcontentsline{toc}{subsection}{Building Bacula with Encryption Support}