On Sunday 12 February 2006 23:07, Landon Fuller wrote:
Landon Fuller wrote:
One other issue worth raising -- The director can currently overwrite
any file on the FD, including the encryption keys or the FD
configuration file, thus exposing private data to the director.
Something else I
On 5 Feb 2006 at 18:33, Landon Fuller wrote:
In the spirit of status reports -- Bacula's File Daemon now has complete
support for signing and encryption data prior to sending it to the
Storage Daemon, and decrypting said data upon receipt from the Storage
Daemon.
That's only the Unix
On Feb 14, 2006, at 13:50, Dan Langille wrote:
On 5 Feb 2006 at 18:33, Landon Fuller wrote:
In the spirit of status reports -- Bacula's File Daemon now has
complete
support for signing and encryption data prior to sending it to the
Storage Daemon, and decrypting said data upon receipt from
On 12 Feb 2006 at 13:49, Landon Fuller wrote:
Dan Langille wrote:
On 5 Feb 2006 at 18:33, Landon Fuller wrote:
In the spirit of status reports -- Bacula's File Daemon now has complete
support for signing and encryption data prior to sending it to the
Storage Daemon, and decrypting
On 12 Feb 2006 at 14:07, Landon Fuller wrote:
Landon Fuller wrote:
One other issue worth raising -- The director can currently overwrite
any file on the FD, including the encryption keys or the FD
configuration file, thus exposing private data to the director.
Something else I forgot
Dan Langille wrote:
On 12 Feb 2006 at 14:07, Landon Fuller wrote:
Kern, is it reasonable to assume that the Storage Daemon will always
provide per-file stream data in the order it was written by the File
Daemon? If not, I'd guess the alternative is to cache the file
attributes on restore and
On 13 Feb 2006 at 9:02, Phil Stracchino wrote:
Dan Langille wrote:
On 12 Feb 2006 at 14:07, Landon Fuller wrote:
Kern, is it reasonable to assume that the Storage Daemon will always
provide per-file stream data in the order it was written by the File
Daemon? If not, I'd guess the
Dan Langille wrote:
On 5 Feb 2006 at 18:33, Landon Fuller wrote:
In the spirit of status reports -- Bacula's File Daemon now has complete
support for signing and encryption data prior to sending it to the
Storage Daemon, and decrypting said data upon receipt from the Storage
Daemon.
Now
Landon Fuller wrote:
One other issue worth raising -- The director can currently overwrite
any file on the FD, including the encryption keys or the FD
configuration file, thus exposing private data to the director.
Something else I forgot to mention; the file daemon also ensures data
