From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Miller's 9pi image (rpi4) problems
Date: Fri, 11 Jun 2021 17:00:43 +0100 [thread overview]
Message-ID: <9ceba0b9643a4184fb064f423c29f7d2@hamnavoe.com> (raw)
In-Reply-To: <YMN1VeHFrTZqHfxh@SDF.ORG>
> I can connect to github too, and some other places. But if you surf the web
> you'll end up with this error. Just a few If you want to do a test:
>
> https://developer.arm.com
> https://wikipedia.org
> https://marc.info
> https://www.perseus.tufts.edu
> http://mars.jpl.nasa.gov
Thanks, I did a test:
term% hget https://wikipedia.org
tlsClient: could not negotiate acceptable security parameters
What most of these sites have in common is that they allow only ECDHE key exchange
for tls1.2, which I think is not currently implemented in either 4e or 9legacy.
Any volunteers?
The last example is a weird one:
term% hget https://mars.jpl.nasa.gov
tlsClient: devtls expected ver=303, saw (len=2) type=15 ver=0 '\x15'
I'll let somebody else try to diagnose that!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc5dcd85d69518168-M6c2f870f7a6a43355b2f2cf1
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-11 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 18:59 adr via 9fans
2021-06-11 9:05 ` Richard Miller
2021-06-11 9:14 ` Richard Miller
2021-06-11 14:38 ` adr via 9fans
2021-06-11 16:00 ` Richard Miller [this message]
2021-06-11 16:13 ` adr via 9fans
2021-06-11 16:26 ` Richard Miller
2021-06-11 17:57 ` adr via 9fans
2021-06-11 18:18 ` Richard Miller
2021-06-11 18:50 ` a
2021-06-11 19:10 ` hiro
2021-06-11 21:07 ` adr via 9fans
2021-06-13 17:22 ` [9fans] " adr via 9fans
2021-06-17 15:05 ` [9fans] " Steve Simon
2021-06-17 19:48 ` adr via 9fans
2021-06-19 11:41 ` adr via 9fans
2021-06-19 12:44 ` Richard Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ceba0b9643a4184fb064f423c29f7d2@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).