hi, > This is great. I'd be interested to know where you got stuck, and if > you had any suggestions for improving the TLS code at all (error > messages, configuration settings, etc).
the main problem was the docs, the TLS example is difficult to follow because the hostnames and so forth being used isnt clear, so you arent always sure what is connecting to what and what cert to use. As for error messages, I know there were one really confusing one, don't remember the actual error message but it was when I had a client connecting where the hostname and the CN in the cert didnt match. In the example in the docs the cert CN's have things like [EMAIL PROTECTED] in the CN, but I found if CN != hostname it just wont work, so that was a bit missleading as well. The docs also doesn't show that you need to put any TLS stuff in the Client resources, I think mine covers all of the above you're welcome to take it and use it in the official documentation or whatever. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
