From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tls 1.2
Date: Tue, 15 Nov 2016 16:22:38 +0000 [thread overview]
Message-ID: <d3246e2621a48dbd0c3cb2a4d4e7c581@quintile.net> (raw)
In-Reply-To: <CANUoZoEvnFZroCStHxrUKx_tqQ8MjvTNin2dQqim-bw3CHSmVg@mail.gmail.com>
> Just to be sure. Have you rebuilt libsec as well?
yep.
Wireshark sees TLS 1.2 packets from plan9 so I have that much right...
-Steve
prev parent reply other threads:[~2016-11-15 16:22 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
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 [this message]
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=d3246e2621a48dbd0c3cb2a4d4e7c581@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).