I think that might be the better solution.
and not any intermediates in that persons keychain or other certificate stores.
#DELETE MUMBLE CERTIFICATE ON SERVER VERIFICATION#
This verification would only use the certificates in the. But I'm not sure it'd do much good for anyone else.Īn alternative to this, would be to have the Certificate Wizard verify the client certificate chain and show a good/bad indicator in the Wizard. Certificates allow you to register directly with a server, without having to use an external website or program. That would at least give people who are familiar with the terms "certificate chain" and "intermediate certificate" a chance to act. Please include all intermediate certificates and try again.". I think that should satisfy the request, but we'd still be using SSL-speak to convey the error message to the user: "Your client's certificate chain is not complete. We could then potentially walk the chain and check for the specific case of missing intermediate certificates. If the server tells the client that SSL Error: The root CA certificate is not trusted for this purpose, the server must be complaining about the client's certificate chain. We should probably make it clearer, if possible. Edit the /etc/mumble-server.ini, and change serval info there.
#DELETE MUMBLE CERTIFICATE ON SERVER INSTALL#
It is thus missing some details like original creator etc. My newly installed public mumble server is configured in these step: Add the ppa repo to apt, and apt-get install it, and dpkg-reconfigure it. This ticket has been migrated from sourceforge. I can attach the public certificates if needed. I found this rather odd as it is signed by the same CA as defined in mumble-server.ini (sslCA). My certificate in question is signed by my own CA, which would explain the trust issue with the server. SSL Error: The root CA certificate is not trusted for this purpose Having looked at the server log for my private team's server I found this: I would consider it a bug that an issue with the client certificate is not told to the user for the reason that the connection failed. I generated a fresh one within Mumble and I could connect to servers. Every connection attempt was immediately dropped with "Server connection failed: The remote host closed the connection.".ĭireFog suggested it may be a certificate issue. I was unable to connect to any Mumble server (including my private team one).
0 kommentar(er)
