On 4 Sep 2006 at 17:42, Kern Sibbald wrote: > On Monday 04 September 2006 16:53, Dan Langille wrote: > > I've found that "TLS Require = yes" stops comms from working. > > > > I needed "TLS Enable = yes". This is with a 1.38.8 Director and a > > bacula-client-1.38.11_1. Does that make sense? With just ""TLS > > Require = yes" and not "TLS Enable = yes", I get: > > > > 04-Sep 10:45 bacula-dir: *Console*.2006-09-04_10.45.22 Fatal error: > > Authorization problem: Remote server did not advertise required TLS > > support. > > > > If I change to "TLS Enable = yes", then the status command works. > > > > The bacula-fd.conf specifies: > > > > TLS Enable = yes > > TLS Require = yes > > > > If more details are required, I can provide them. > > That sounds perfectly logical to me.
OK, then let me add to the equation. With this in the client resource on bacula-dir.conf: TLS Require = yes TLS Enable = yes And this in the bacula-fd.conf: TLS Enable = yes TLS Require = yes we get: Fatal error: Authorization problem: Remote server did not advertise required TLS support. If I remove "TLS Require = yes" from bacula-dir.conf, status works just fine. -- Dan Langille : Software Developer looking for work my resume: http://www.freebsddiary.org/dan_langille.php ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
