From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Richard Stallman <rms@gnu.org>
Cc: Eric Marsden <eric.marsden@risk-engineering.org>, emacs-devel@gnu.org
Subject: Re: ALPN support for GnuTLS connections
Date: Sat, 09 Nov 2024 00:17:07 +0200 [thread overview]
Message-ID: <34594.9180353031$1731104272@news.gmane.org> (raw)
In-Reply-To: <E1t37bA-0002Ei-Pi@fencepost.gnu.org> (Richard Stallman's message of "Tue, 22 Oct 2024 01:38:28 -0400")
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> ALPN sounds useful and a good thing for Emacs to support.
> But could you tell me a little more about this point?
>
> > For a service provider who makes it possible to access PostgreSQL
> > over the internet, there are many benefits to the new ALPN-based mechanism, such
> > as allowing the use of commercial “TLS gateways” (that do no application-level
> > processing) as entrypoints to their network. I expect that over time, an
> > increasing proportion of internet services will require ALPN.
>
> What is a TLS gateway, and what would a usage scenario look like?
> Who would choose to use one -- would it be the server, or the client?
>
> In particular, if you are running your own server and you could set up
> whatever network access methods you like, why would someone use a
> "gateway" to talk with your server? And presuming a decision to do
> that, why would someone want to use a "commercial" one?
A gateway can be something simple as a webserver as reverse proxy that protects a
program that can't do load balancing, does do tls or any other reason
why the application HTTP server shouldn't be exposed directly to the
internet.
next prev parent reply other threads:[~2024-11-08 22:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 8:23 ALPN support for GnuTLS connections Eric Marsden
2024-09-30 9:21 ` Robert Pluim
2024-09-30 10:21 ` Eric Marsden
2024-09-30 13:13 ` Robert Pluim
2024-09-30 17:26 ` Eric Marsden
2024-10-07 8:22 ` Robert Pluim
2024-10-10 13:54 ` Robert Pluim
2024-10-10 16:23 ` Eli Zaretskii
2024-10-11 7:32 ` Robert Pluim
2024-10-12 9:30 ` Eric Marsden
2024-10-14 9:22 ` Robert Pluim
2024-10-15 7:06 ` Eric Marsden
2024-10-18 12:37 ` Robert Pluim
2024-10-15 3:02 ` Richard Stallman
2024-10-15 7:33 ` Eric Marsden
2024-10-22 5:38 ` Richard Stallman
2024-10-31 13:31 ` Eric Marsden
2024-11-08 22:17 ` Björn Bidar [this message]
[not found] ` <87fro1jrq4.fsf@>
2024-11-11 5:12 ` Richard Stallman
2024-11-11 17:15 ` Björn Bidar
[not found] ` <87y11pu1x4.fsf@>
2024-11-15 4:45 ` Richard Stallman
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='34594.9180353031$1731104272@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=emacs-devel@gnu.org \
--cc=eric.marsden@risk-engineering.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.