On Wed, 30 Sep 2009 13:38:02 +0200, baculalist wrote: > Hello List, > > Although there's some information on 'Dealing_with_Firewalls.html' about > this, it seems to not describe the solution to this problem. > > Problem: > A single storage daemon listens on 64.12.34.56 AND 192.168.1.2, and > provides a certificate (myhost.domain.com corresponding to 64.12.34.56) > to incoming connections from directors and file daemons. Incoming > connections to 192.168.1.2 fail, because mycert.domain.com only resolves > to the first of the two IP addresses. The configuration keyword TLS > Require is set to 'yes' (as it should be.)
this is IMHO an known problem to TLS/SSL certificates. on http servers you can get around with setting the subjectAltName of the certificate to the other dns names. Don't know if this works too for bacula and don't know if this is a standard or just "best practice". clearly i would say this is not a task that needs to be fixed in bacula, - Thomas ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
