From: Nathan Owens <nathan@nathan.io>
To: "Rodney W. Grimes" <starlink@gndrsh.dnsmgr.net>
Cc: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Dumping and extracting the SpaceX Starlink User Terminal firmware | COSIC
Date: Fri, 9 Jul 2021 05:50:46 -0700 [thread overview]
Message-ID: <CALjsLJuZYZWTx+iUEc952jH=MT6Qwr5vGrDxgJcNjCK=ddw0vA@mail.gmail.com> (raw)
In-Reply-To: <202107091249.169CnRGU041512@gndrsh.dnsmgr.net>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
> At the time of writing we were able to obtain a root shell on the UT, but
it’s too early to publicly share more information on that matter.
They say they got root shell..
On Fri, Jul 9, 2021 at 5:49 AM Rodney W. Grimes <starlink@gndrsh.dnsmgr.net>
wrote:
> > they were able to read from the flash storage on the dish and get a root
> shell
> > on it.
>
> I do not believe they got a root shell, the terminal is locked down
> fairly well by use of a fuse map. Unless I missed something, they
> never got past that issue.
>
> >
> >
> https://www.esat.kuleuven.be/cosic/blog/dumping-and-extracting-the-spacex-starlink-user-terminal-firmware/
> >
> > David Lang
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
> >
> >
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1892 bytes --]
prev parent reply other threads:[~2021-07-09 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 18:23 David Lang
2021-07-08 19:17 ` Gary E. Miller
2021-07-09 12:49 ` Rodney W. Grimes
2021-07-09 12:50 ` Nathan Owens [this message]
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='CALjsLJuZYZWTx+iUEc952jH=MT6Qwr5vGrDxgJcNjCK=ddw0vA@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=david@lang.hm \
--cc=starlink@gndrsh.dnsmgr.net \
--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