From: Michael Richardson <mcr@sandelman.ca>
To: "David P. Reed" <dpreed@deepplum.com>, "Livingood\,
Jason" <Jason_Livingood@comcast.com>,
"starlink\@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] something of a step backwards
Date: Mon, 15 Nov 2021 17:36:06 -0500 [thread overview]
Message-ID: <24348.1637015766@localhost> (raw)
In-Reply-To: <1637001937.876717373@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
David P. Reed <dpreed@deepplum.com> wrote:
> The mechanism for MITM'ing HTTPS connections is well known. I don't
> intend to detail it here, but it is based on the fact that certs aren't
> properly validated by client-end software and server-end software.
No, this is just not the case.
While there are occasionally issues that affect some strange corner case,
there are no issues in browsers available on any platforms I know of.
It can only be done in Enterprise cases where the Enterprise uses a
management system to push new anchors. That part is "well-known".
As for blaming protocols when the fault is bufferbloat, you are definitely
right on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2021-11-15 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1636650001.22273.starlink@lists.bufferbloat.net>
2021-11-11 18:30 ` David P. Reed
2021-11-15 14:21 ` Livingood, Jason
2021-11-15 18:45 ` David P. Reed
2021-11-15 22:36 ` Michael Richardson [this message]
2021-11-11 15:53 Dave Taht
2021-11-11 15:54 ` Nathan Owens
2021-11-11 18:14 ` Jonathan Bennett
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
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24348.1637015766@localhost \
--to=mcr@sandelman.ca \
--cc=Jason_Livingood@comcast.com \
--cc=dpreed@deepplum.com \
--cc=starlink@lists.bufferbloat.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