From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Security Find
Date: Fri, 17 Dec 2021 08:04:32 -0800 [thread overview]
Message-ID: <CAA93jw5YGBMcUOZrS=Fae_L2LN-aeSuaPn5RwefP6RN2fkq8Kg@mail.gmail.com> (raw)
In-Reply-To: <CAHtUBuhKK2hfgJL8kGu=_+f8uSkZ-pEEpZwMvjVqQLHV5sDkfQ@mail.gmail.com>
Nice work, Jonathan! You buried the lede... A lot simpler than the
other two bugs you discussed, either one of which has me inclined to
log out permanently and head to mexico. Why do we get all these
security vulns at christmas? I lost a christmas to spectre, another to
a mips fpu bug, another to the ping of death - I remember how I spent
those christmases far more clearly than the actual "fun" ones.
Also nice to see the 28ms RTT between you and your friend. Care to try
a few flent tests between you? or to the internet?
Over here I've been doing some pretty extensive tests of my starlink
test cloud, from a dsl and a cable modem, the cake rtt_fair results
(from dallas to sydney) were to die for:
https://forum.mikrotik.com/viewtopic.php?p=898777#p898627
On Fri, Dec 17, 2021 at 7:47 AM Jonathan Bennett
<jonathanbennett@hackaday.com> wrote:
>
> Thought you guys might appreciate this. A traceroute lead to a Starlink bug bounty. https://hackaday.com/2021/12/17/this-week-in-security-log4j-pdf-cpu-and-i-hack-starlink/
>
> --Jonathan Bennett
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-12-17 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:46 Jonathan Bennett
2021-12-17 16:04 ` Dave Taht [this message]
2021-12-17 16:39 ` David Lang
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='CAA93jw5YGBMcUOZrS=Fae_L2LN-aeSuaPn5RwefP6RN2fkq8Kg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=jonathanbennett@hackaday.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