User Tools

Site Tools


This is an old revision of the document!

Untrusted Director

I ran into a situation where the director and storage systems weren't trusted by the fd client. Ie, some of the data on the client should not be available to the director. Nor should the director have rights to create or delete critical files on the client.

The approach I took was to:

  1. create a chroot environment to run the bacula fd client in. The bacula client does not run as root.
  2. create a cron script to copy the files that need to be backed up into the chroot area. This script uses gpg to encrypt and compress the files before copying.

The result is that bacula is used to backup selected files without trusting the bacula system. File names are still exposed but I wasn't concerned about that.


# compress and encrypt files and then copy to a directory where bacula will get them
# don't update files that haven't changed

export DIR

cd xxx

for i in *
   if test -f "$i"
      if test -f "$DIR/$i" -a  "$DIR/$i" -nt "$i"
          gpg --compress-algo bzip2 --passphrase xxxxxxxxx --no-use-agent -c  < "$i" > "$DIR/$i"
hints_tips/untrusted_director_-_nix_solution.1236701896.txt.gz · Last modified: 2009/03/10 16:18 by jzeeff