Got it figured out. I'll post what I did just in case anyone goes looking for
it.
On my windows client I added the bold part to c:\Program
Files\Bacula\bacula-fd.conf
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 5.2.3 (12/16/11) -- Windows MinGW32
#
# There is no
I was following
http://www.bacula.org/en/dev-manual/main/main/Data_Encryption.html and am a
little confused.
I am a Linux noob. I have got Bacula up and running, everything tweaked and
going smooth. I am now being told that we need to encrypt one of my client
machine's data during the backup.
Hi Jon,
2011/10/11 Jon Schewe
> Is there any reason (besides good security) that I can't use the same
> private key for all bacula clients? Can I use the same pem file as well?
>
> Jon
>
>
Works fine for me here... I'm not trying to protect my machines' data from
each other, only to ensure it's
Is there any reason (besides good security) that I can't use the same
private key for all bacula clients? Can I use the same pem file as well?
Jon
--
All the data continuously generated in your IT infrastructure contains a
Does anybody know what happens if the generated encryption key pair expires?
Will I be able to restore encrypted backups?
openssl genrsa -out master.key 2048
openssl req -new -key master.key -x509 -out master.cert -days 1
openssl genrsa -out fd-test.key 2048
openssl req -new -key fd-test.key -
