>>>>> On Sat, 7 Nov 2026 10:05:56 +0100, Stefan G Weichinger said:
> 
> Am 05.11.26 um 17:51 schrieb Martin Simmons:
> > Instead, it works by generating a random encryption key (called the session
> > key) to encrypt the data and writes the session key to the volume, encrypted
> > with the public key in the PKI Keypair file.  This allows the session key to
> > be decrypted using the private key in that file and then the data can be
> > decrypted using the session key.
> > 
> > If you also provide the PKI Master Key directive, then it writes a second 
> > copy
> > of the session key encrypted with the master public key in that file.  This
> > allows the session key to also be decrypted using the master private key 
> > after
> > following the instructions in
> > https://docs.baculasystems.com/BEAdvancedFeaturesUsage/DataEncryption/FileDaemonEncryption/DecryptingWithMasterKey/index.html
> Ah, OK, so it's basically a backup set of keys, right?

Yes.

> I am no crypto expert: why is the FD key*pair* used, but only the master 
> public *key* ? Just curious, while we're at it ;-)

A keypair is needed to allow the FD to decrypt a backup during restore.  The
reason for only giving the master public key to the FD initially (except in
the DecryptingWithMasterKey scenario) is because the master key might be
shared with other FDs, so keeping it secret is better for security in case an
FD is hacked.

You can have multiple backup keys instead of a single master key, but that is
more complicated to administer.

__Martin


_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to