On 18.11.2016 at 13:03 wrote Niall Hallett: > Hi, > > I'm trying to setup jobs to securely backup remote clients. We > already have a wildcard cert *.xxxxx.com but when I try running a > job, it reports: > > 18-Nov 11:37 bareos-dir JobId 0: Fatal error: bnet.c:192 TLS host > certificate verification failed. Host name "client.xxxxx.com" did not > match presented certificate. > > Do I have to generate individual certificates for each client?
I've not checked, if wild card certificates are supposed to work. However, using "TLS Allowed CN" you can define, what CN is expected. So create a certificate with CN = "allmyclients.example.com" and setting them to TLS Allowed CN = "allmyclients.example.com" should work. Probably this also works with TLS Allowed CN = "*.xxxxx.com". Jörg -- Jörg Steffens [email protected] Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
