Ok, much appreciated. For those reading, I'm pivoting to this phrasing.
--
Could not connect to example.com due to an unverified certificate.
You can address this by downloading the certificate from a source your
operating system trusts (to mitigate man-in-the-middle attacks), then adding
the
Yes, that's right.
Ryan
On Mon, Apr 12, 2021 at 4:23 PM Sage Gerard wrote:
> Understood, thank you. By "trusted location," do you mean a server with a
> certificate that operating systems already trust?
> On 4/12/21 10:15 AM, Ryan Culpepper wrote:
>
> Racket does not provide a way to do that.
Understood, thank you. By "trusted location," do you mean a server with a
certificate that operating systems already trust?
On 4/12/21 10:15 AM, Ryan Culpepper wrote:
> Racket does not provide a way to do that.
>
> You can use `openssl s_client -showcerts -connect host:port < /dev/null` to
>
Racket does not provide a way to do that.
You can use `openssl s_client -showcerts -connect host:port < /dev/null` to
get the server's certificate chain in PEM form (with other logs around it).
Of course, an attacker could intercept the connection and send you their CA
certificate instead. It
When ssl-connect fails due to an untrusted certificate, this error is
raised:
ssl-connect: connect failed (error:1416F086:SSL
routines:tls_process_server_certificate:certificate verify failed)
I'd like to give the user a more helpful error, like this:
Could not connect due to an untrusted
5 matches
Mail list logo
