Landon Fuller wrote:
>> To rephrase the question:
>>
>> I would like to require some (remote) clients to communicate encrypted
>> with the storage daemon, and some other (local) clients not.
>>
>> Is this possible? Maybe I need two storage daemons for that? (but two
>> storage daemons sharing a device is probably not possible?).
>> Or is it okay to configure the storage daemon with "TLS Require = no"
>> and the remote clients will connect encrypted nevertheless, because in
>> their configuration (file daemon) is set: "TLS Require = yes"?
>>
>> Any help with this would be greatly appreciated,
> 
> Specifying "TLS Require = yes" in the bacula-fd.conf FileDaemon {}
> section should result in TLS being required for all outgoing storage
> connections.
> You could test this by setting TLS Enable = no on the storage daemon and
> verifying that the file daemon refuses to connect.

Thanks, worked like a charm. I should have come up with this test by
myself...

Thanks,

Timm


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users