From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Maintenance of an auth server files vs a dns+dhcp+tftp server
Date: Wed, 16 Nov 2016 01:21:15 +0100 [thread overview]
Message-ID: <5d0af46ac703f7f8baef2e8f0f6f64ae@felloff.net> (raw)
In-Reply-To: <85c461917203564b5f989b4f552d1d7d@quintile.net>
you might take a look at 9front devtls and libsec. it does support
tls1.1 and tls1.2. including ecdsa, ecdhe, both variants of
chacha20-poly1305 and aes-gcm aead ciphers suits...
i updated drawterm with the code and try to keep it in sync and
should not be too difficult to port back to labs plan9.
--
cinap
next prev parent reply other threads:[~2016-11-16 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 17:00 James A. Robinson
2016-11-15 17:10 ` Steve Simon
2016-11-16 0:21 ` cinap_lenrek [this message]
2016-11-16 0:24 ` James A. Robinson
2016-11-15 18:47 ` Stanley Lieber
2016-11-15 18:53 ` James A. Robinson
2016-11-15 19:05 ` Stanley Lieber
2016-11-15 19:22 ` James A. Robinson
2016-11-15 19:52 ` Ole-Hjalmar Kristensen
2016-11-15 20:06 ` Stanley Lieber
2016-11-15 20:12 ` cinap_lenrek
2016-11-16 13:21 ` Anthony Sorace
2016-11-16 15:31 ` Stanley Lieber
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=5d0af46ac703f7f8baef2e8f0f6f64ae@felloff.net \
--to=cinap_lenrek@felloff.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).