From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] libsec, pushtls, tlssrv: add support for Server Name Indication (SNI) extension
Date: Thu, 25 Jan 2024 13:11:37 +0100 [thread overview]
Message-ID: <5F1FF7E81205A7A089331E5C7C69C5F9@felloff.net> (raw)
In-Reply-To: <229D405D66A4143A9080A3D8FD494A0F@9lab.org>
I think you'd really want to have a new tlsServerX() function for this
with a callback to provide the certificate giving the server name.
Or alternatively we pass a whole array of certificates in,
and the server matches the certificate subject(s). For that
programs could maybe accept multiple -c arguments.
Hardcoding some path with achmed in there feels very wrong.
The whole SNI stuff is a gigant layer-violation in my opinion,
and if you use it, you are going to want to expose the effective
server name (like putenv() in tlssrv).
--
cinap
next prev parent reply other threads:[~2024-01-25 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 11:32 igor
2024-01-25 12:11 ` cinap_lenrek [this message]
2024-01-25 12:51 ` igor
2024-01-25 15:14 ` cinap_lenrek
2024-01-26 7:21 ` igor
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=5F1FF7E81205A7A089331E5C7C69C5F9@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).