Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-23 Thread Kern Sibbald
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 e

[Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-14 Thread Landon Fuller
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

[Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-14 Thread Dan Langille
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 b

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-13 Thread Dan Langille
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 t

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-13 Thread Phil Stracchino
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 resto

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-13 Thread Dan Langille
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

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-13 Thread Dan Langille
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, a

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-12 Thread Landon Fuller
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 integrit

Re: [Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-12 Thread Landon Fuller
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 t

[Bacula-users] Re: [Bacula-devel] Encryption Status

2006-02-09 Thread Dan Langille
resent, this time to bacula-users, the list upon which this thread started. 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 decrypt