Hi!
I can strip down the HTTPS example in the manual to the bare minimum, turn it into accessing HTTP, NEX, NNTP and other protocols, add back TLS to e.g. access NNTPS, but with the average Gemini server I'm biting on granite.
Not really understanding the error OpenSSL shows, I just assume that it fails with servers using self signed certificates and succeeds with some others because they (re)use a (sub)domain they already have registered with some authority for their HTTPS server.
Similarily they seem to succeed or fail using Ncat to access them depending on using "-ssl" or "-ssl-verify" to connect.
Is there a way to teach Gambit an additional option for make-tls-context to do similar?
Afficher les réponses par date
Hi. I’m not a openssl expert and don’t know how to help you. Could you rephrase the problem as a github repo issue so that the problem can be reproduced and perhaps I or someone else can find a solution?
Marc
On Apr 22, 2024, at 10:50 AM, yeti yeti@tilde.institute wrote:
Hi!
I can strip down the HTTPS example in the manual to the bare minimum, turn it into accessing HTTP, NEX, NNTP and other protocols, add back TLS to e.g. access NNTPS, but with the average Gemini server I'm biting on granite.
Not really understanding the error OpenSSL shows, I just assume that it fails with servers using self signed certificates and succeeds with some others because they (re)use a (sub)domain they already have registered with some authority for their HTTPS server.
Similarily they seem to succeed or fail using Ncat to access them depending on using "-ssl" or "-ssl-verify" to connect.
Is there a way to teach Gambit an additional option for make-tls-context to do similar?
-- I do not bite, I just want to play.
Gambit-list mailing list -- gambit-list@iro.umontreal.ca To unsubscribe send an email to gambit-list-leave@iro.umontreal.ca
Marc Feeley via Gambit-list gambit-list@iro.umontreal.ca writes:
Hi. I’m not a openssl expert
Neither am I.
and don’t know how to help you. Could you rephrase the problem as a github repo issue so that the problem can be reproduced and perhaps I or someone else can find a solution?
I'll try.
Thanks!
_o/"
The way I use to get around it was to sed -i -e 's#SSL_VERIFY_PEER#SSL_VERIFY_NONE#g lib/os_io.c
On Monday, April 22nd, 2024 at 11:13 AM, yeti yeti@tilde.institute wrote:
Marc Feeley via Gambit-list gambit-list@iro.umontreal.ca writes:
Hi. I’m not a openssl expert
Neither am I.
and don’t know how to help you. Could you rephrase the problem as a github repo issue so that the problem can be reproduced and perhaps I or someone else can find a solution?
I'll try.
Thanks!
_o/"
-- I do not bite, I just want to play.
Gambit-list mailing list -- gambit-list@iro.umontreal.ca To unsubscribe send an email to gambit-list-leave@iro.umontreal.ca
Jaime Fournier jaimef@linbsd.org writes:
The way I use to get around it was to sed -i -e 's#SSL_VERIFY_PEER#SSL_VERIFY_NONE#g lib/os_io.c
Thanks!
I glued that all together as an issue.
-
Jaime Fournier -
Marc Feeley -
yeti