From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] TLS 2.x
Date: Fri, 21 Apr 2017 14:15:42 +0100 [thread overview]
Message-ID: <54fe423c902c1aaf00dff14d28595932@quintile.net> (raw)
Hi,
I am running richard Miller's Raspberry pi kernel.
I want to update my TLS so I can use modern https.
I have lifted the /sys/src/libsec from 9front, built that
and rebuilt my kernel to use it - devssl.c doesn't seem to have changed.
Unfortunately I still have problems:
hget https://xxx...
tlsClient: Hangup
tlsClient: Hangup
tlsClient: Hangup
etc.
Have I missed a step (is there somthing else I need to update?),
or have I just messed it up?
-Steve
next reply other threads:[~2017-04-21 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 13:15 Steve Simon [this message]
2017-04-21 13:28 cinap_lenrek
2017-04-21 13:42 cinap_lenrek
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=54fe423c902c1aaf00dff14d28595932@quintile.net \
--to=steve@quintile.net \
--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).