Hello Phillip
> > One more question: > > > >> The private key file is only needed to be able to load the certificates. > >> It has nothing to do with > >> the connection itself. > > How does the storage daemon, the director, or the file daemon know about > > the name of the file > > containing the private key ? It seems to be nowhere defined in the > > configuration files. > > Please see in the docs: > http://doc.bareos.org/master/html/bareos-manual-main-reference.html#ExampleTLSConfigurationFiles > > I guess you are looking for the directive "TLS Key"? Probably:-) I thought, it is references the public key. I checked my (now working) setup, and found that also I have referenced the private key there. In https://de.wikipedia.org/wiki/Transport_Layer_Security, and in particular in https://de.wikipedia.org/wiki/Transport_Layer_Security#/media/File:SSL_handshake_with_two_way_authentication_with_certificates.svg, there is the handshake of TLS described. Besides the exchange of signatures, it requires the exchange of public keys in preparation of a secure connection. A reference to the public key seems not to be stored in the configuration file. Is it computed from the private key and sent then over to the other party ? Thanks Tilman -- 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.
