From: David du Colombier <0intro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] tls 1.2
Date: Tue, 15 Nov 2016 17:00:32 +0100 [thread overview]
Message-ID: <CANUoZoGp+Ex4CYHx=CrQtSf1n=Lbpq_RqDVuyFemX9YcP=6Rwg@mail.gmail.com> (raw)
In-Reply-To: <e86c152dd5929622f20e185b03573638@quintile.net>
> I am trying to get tls 1.2 working on a labs build of plan9.
>
> What is most infuriating is I am sure I did this a few years ago but I cannot remember
> how (or even if) I got it working.
>
> what I have done is to install the following patches from 9legacy:
>
> libsec-chacha.diff tls-devtls12.diff
> libsec-tlshand12-norc4.diff tls-tlshand12.diff
> libsec-tlshand12-nossl3.diff
>
> and rebuild my kernel and upas (where I need TLS1.2).
>
> When I try to connect to a windows machine I get an error
> from devtls in the kernel of the length of the message is incorrect.
>
> I have hacked around inside port/devtls.c but not found anything obvious,
> I have also played with wireshark which didn't see anything very wrong.
>
> I am sure I have missed an obvious step but I cannot see what it is.
The libsec-chacha.diff patch is not useful, since it's not used yet.
Does it works when you connect to https://9p.io/?
This machine have the same patches applied.
--
David du Colombier
next prev parent reply other threads:[~2016-11-15 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 15:48 Steve Simon
2016-11-15 15:55 ` hiro
2016-11-15 16:23 ` Steve Simon
2016-11-15 16:00 ` David du Colombier [this message]
2016-11-15 16:22 ` Steve Simon
2016-11-16 8:18 ` David du Colombier
2016-11-15 16:03 ` David du Colombier
2016-11-15 16:22 ` Steve Simon
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='CANUoZoGp+Ex4CYHx=CrQtSf1n=Lbpq_RqDVuyFemX9YcP=6Rwg@mail.gmail.com' \
--to=0intro@gmail.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).