From: Larry Press <lpress@csudh.edu>
To: Hesham ElBakoury <helbakoury@gmail.com>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Reverse Engineering
Date: Sat, 9 Sep 2023 03:58:22 +0000 [thread overview]
Message-ID: <BYAPR03MB3863982C235F62212C66AF4AC2ECA@BYAPR03MB3863.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAFvDQ9p9XqaBFM_2iH7SJ3hjm0k50zOTqDiPWXxpwcvq118LnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Why does Elon Musk object to the use of Starlink for navigation?
Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of Hesham ElBakoury via Starlink <starlink@lists.bufferbloat.net>
Sent: Friday, September 8, 2023 5:27:22 PM
To: starlink@lists.bufferbloat.net <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink Reverse Engineering
This MIT Technology Review report provides the details of the work done by Professor Humphrey and his team to reverse engineer starlink signals: https://www.google.com/amp/s/www.technologyreview.com/2022/10/21/1062001/spacex-starlink-signals-reverse-engineered-gps/amp/<https://urldefense.com/v3/__https://www.google.com/amp/s/www.technologyreview.com/2022/10/21/1062001/spacex-starlink-signals-reverse-engineered-gps/amp/__;!!P7nkOOY!uvKxQt1rcYRmzqkpdhQQiPVH9sJm19Cf-5iUpkIm4CqaB1VyomQeC4Sft16J9XFVTEvRugU8VOdCc58FEM1WD25_ZQ$>
It is worth it to mention that Elon Musk does not like using starlink for navigation which is the motivation behind Humphrey
Although the report mentions Humphrey non-peer reviewed paper, actually the peer-reviewed paper has been published here
https://ieeexplore.ieee.org/abstract/document/10107477?casa_token=ws8yh0wRnRsAAAAhA:Q0LZ3Gt-vxKsGQ170OhIp4X4tQoa_U2m6DlBKY7a-A0EYxTzRd4VLzpHkZKSglEPiMEJKK4XTHk<https://urldefense.com/v3/__https://ieeexplore.ieee.org/abstract/document/10107477?casa_token=ws8yh0wRnRsAAAAA:Q0LZ3Gt-vxKsGQ170OhIp4X4tQoa_U2m6DlBKY7a-A0EYxTzRd4VLzpHkZKSglEPiMEJKK4XTHk__;!!P7nkOOY!uvKxQt1rcYRmzqkpdhQQiPVH9sJm19Cf-5iUpkIm4CqaB1VyomQeC4Sft16J9XFVTEvRugU8VOdCc58FEM0kG4phIg$>
Hesham
[-- Attachment #2: Type: text/html, Size: 2615 bytes --]
next prev parent reply other threads:[~2023-09-09 3:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:27 Hesham ElBakoury
2023-09-09 3:58 ` Larry Press [this message]
2023-09-09 4:15 ` David Lang
2023-09-09 4:53 ` Hesham ElBakoury
2023-09-14 9:14 ` Alexandre Petrescu
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=BYAPR03MB3863982C235F62212C66AF4AC2ECA@BYAPR03MB3863.namprd03.prod.outlook.com \
--to=lpress@csudh.edu \
--cc=helbakoury@gmail.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