revolutions per minute - a new metric for measuring responsiveness
 help / color / mirror / Atom feed
From: Christoph Paasch <cpaasch@apple.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: Randall Meyer <rrm@apple.com>, rpm@lists.bufferbloat.net
Subject: Re: [Rpm] Does RPM measurement *require* a valid SSL certificate
Date: Thu, 14 Oct 2021 13:27:05 -0700	[thread overview]
Message-ID: <YWiSmRqTSzBQxvxU@MacBook-Pro-2.local> (raw)
In-Reply-To: <8F8B59C1-9FB7-4B3E-9C15-14180721FEA8@gmail.com>

On 10/13/21 - 17:57, Rich Brown via Rpm wrote:
> 
> > On Oct 13, 2021, at 3:45 PM, Randall Meyer <rrm@apple.com> wrote:
> > 
> > We could add a “—insecure/-k” switch as a feature enhancement to the CLI.
> 
> Or maybe just ignore the certificate. More options is worse, if you have to implement/explain/justify them. 

Ignoring is not a good option. Otherwise, traffic could be intercepted and
one could cheat its RPM-value by having a local termination-point on its AP.


Christoph

> 
> In the context of an RPM test, where there would be (max) dozens of SSL calculations per second, I suspect that the difference between a self-signed certificate and a "real one" would be negligible.
> 
> Thanks.
> 
> Rich

> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm


  reply	other threads:[~2021-10-14 20:27 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 [this message]
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
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=YWiSmRqTSzBQxvxU@MacBook-Pro-2.local \
    --to=cpaasch@apple.com \
    --cc=richb.hanover@gmail.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