panic: x509: certificate is valid for Murmur Autogenerated Certificate v2, not <server_address> about gumble HOT 7 CLOSED

The issue here is that the server certificate is not signed by anyone trusted, so you can either:

1. Skip certificate checking entirely (not a good idea, but fine for testing):

   config.TLSConfig.InsecureSkipVerify = true
   

2. Use a certificate that is signed by a CA that your machine trusts.

3. Make the certificate trusted.

I was having some issues with solution 3, in that I was not able to get trusted, murmur generated certificates to be accepted. Additionally, any self-signed certificate that I created and set as trusted could not be used. The only way I managed to get it working was to (a) create a root certificate, then (b) create a new certificate that was signed by the first. After setting my root certificate as trusted, I was able to connect without issue.

from gumble.

Awesome, this is helpful. You can probably tell that I'm not too experienced with certificates.

Thanks!

Just to clarify, is this kind of what you did for your workaround for number 3? I haven't tried it quite yet, just wanted to confirm.

from gumble.

Just to clarify, is this kind of what you did for your workaround for number 3? I haven't tried it quite yet, just wanted to confirm.

That looks about the same. The CA.pl tool may do it for you, but if it doesn't, remember to add the CA cert to your system.

from gumble.

Awesome, thanks for the help.

from gumble.

Hey, just one last quick question. What is different about gumble where it is required to set up a CA cert? Did piepan just skip certificate checking? I'm just asking because it would be a bit of a pain to ask those who use my bot to set up a certificate when they didn't have to do it previously. I'm thinking about just making it a command line option to skip cert checking when launching my bot.

Thanks!

from gumble.

What is different about gumble where it is required to set up a CA cert? Did piepan just skip certificate checking?

That's correct; piepan didn't verify anything, which was very bad.

I have just added gumbleutil.CertificateLockFile which should allow working with self-signed certificates less of a pain.

from gumble.

I have just added gumbleutil.CertificateLockFile which should allow working with self-signed certificates less of a pain.

Oh, awesome! I will definitely check this out.

from gumble.