verify_mode still defaults to peer

[matobinder]

Sorry, if this isn't the right way to do this, write a new issue on this, or just comment on the closed issue. Still very new to writing issues.

So I had written issue #1028 which showed that #968 had changed it so that verify_mode=peer was being set by default
#1028 was closed but I don't think it actually fixed the whole issue.

The other file changed in #968 was the dsl.rb file. Which is still giving me the requirement to specify either "verify_peer: 'none' or an actual ca.

[evanphx]

Oh, quite right. I'll get that fixed and released tomorrow.

[ma11hew28]

I just did gem update puma, but I still get this error. I guess this fix hasn't yet made it into the latest released version of the Puma Ruby gem: 3.6.0. So, I replaced the ssl_bind method on my Macbook Air with the one from master, and the server starts OK now.