From: Rich Brown <richb.hanover@gmail.com>
To: Christoph Paasch <cpaasch@apple.com>
Cc: Randall Meyer <rrm@apple.com>, rpm@lists.bufferbloat.net
Subject: Re: [Rpm] Does RPM measurement *require* a valid SSL certificate
Date: Wed, 20 Oct 2021 14:47:18 -0400 [thread overview]
Message-ID: <4BB78FBC-A808-4787-AD62-BFA0659E4726@gmail.com> (raw)
In-Reply-To: <DA158695-9A5F-4CAE-8675-7D04988F61F4@apple.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
OK. I am convinced and satisfied by this outcome.
> On Oct 20, 2021, at 2:30 PM, Christoph Paasch <cpaasch@apple.com> wrote:
>
>> - People using those clients but specifying a different RPM Server. It'll be one of those implementations from the github networkQuality/server repo, or an OpenWrt package, or random router manufacturer's own built-in RPM Server.
>
> And these users, will already have to specify the custom server in the command-line with the "-C" option. So, it will be easy for them to also specify "-k/--insecure".
- People using Apple's iOS client have no option (today) to specify a custom server. If one becomes available, I imagine it'll have a checkbox that says, "Accept insecure certificate"
- People using Apple's macOS client can use both -C and -k to accept the insecure certificate.
- People using homegrown RPM clients will use the client's options, presumably that match the Apple clients.
Thanks again.
Rich
[-- Attachment #2: Type: text/html, Size: 3139 bytes --]
next prev parent reply other threads:[~2021-10-20 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 19:18 Rich Brown
2021-10-13 19:45 ` Randall Meyer
2021-10-13 21:57 ` Rich Brown
2021-10-14 20:27 ` Christoph Paasch
2021-10-15 15:10 ` Rich Brown
2021-10-15 16:38 ` Toke Høiland-Jørgensen
2021-10-15 17:19 ` Rich Brown
2021-10-15 16:38 ` Jonathan Foulkes
2021-10-20 18:30 ` Christoph Paasch
2021-10-20 18:47 ` Rich Brown [this message]
2021-10-20 23:04 ` Omer Shapira
2021-10-21 11:45 ` Toke Høiland-Jørgensen
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BB78FBC-A808-4787-AD62-BFA0659E4726@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cpaasch@apple.com \
--cc=rpm@lists.bufferbloat.net \
--cc=rrm@apple.com \
/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