-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ben Walton @ 07/24/2011 05:22 AM: > Excerpts from scar's message of Sun Jul 24 00:12:30 -0400 2011: > >> so i tried adding `TLS Allowed CN = "home1"` and still get the same >> error. however, i tried using the `-d 99` switch for bconsole and >> it reveals something helpful: > > You need to make sure that this parameter exactly matches what the > certificate contains. Maybe you didn't enter a fqdn for the CN in the > cert? If so, the value is ok. Otherwise, you should qualify it. >
`TLS Allowed CN` is not required so there's no need to be messing with it at this time. It should be alright to just not define it for now, until we can at least get TLS connections working. Nevertheless, "home1" is the CN I used. -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAk4sST4ACgkQXhfCJNu98qAkxACfeyiWjYWF6cKvfX3Gtz5DBAbl QHEAn1tncm6Naz9MOLf/jUqYo0FfnsGf =aN1n -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
