From: sl@9front.org
To: 9front@9front.org
Subject: NEW BOUNTIES: improve tls(3), SNI support in tlssrv, ICC color profiles
Date: Sat, 30 May 2015 21:46:17 -0400 [thread overview]
Message-ID: <13b016944060652bfd117b8fb487b4a6@u2.inri> (raw)
REVISED:
improve the tls(3) device
$10 - The TLS device implements the record layer protocols of
Transport Layer Security version 1.0 and Secure Sockets Layer version
3.0. It does not implement the handshake protocols, which are
responsible for mutual authentication and key exchange. Wanted: more
ciphers, support for user certificates, support for certificate
verification. ECDSA! ECDHE!
Based on this:
http://okturing.com/src/2886/body
someone may already be close to claiming $10 from me, on this one.
ADDED:
SNI support in tlssrv
$1 - Server Name Indication (SNI) was recently added to tlsclient.
Now, we'd like to be able to serve multiple certificates from a single
instance of tlssrv.
ADDED:
ICC color profiles
$10 - Support for calibrating displays using custom ICC color
profiles. This is most useful for making livable laptops that have
shitty LCD panels.
sl
reply other threads:[~2015-05-31 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13b016944060652bfd117b8fb487b4a6@u2.inri \
--to=sl@9front.org \
--cc=9front@9front.org \
/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).