4 ms·

This WIRED article[1] references a release of tools and information about the research on GitHub[2] however it 404s. Hope that is not being censored. [1] https

This WIRED article[1] references a release of tools and information about the research on GitHub[2] however it 404s. Hope that is not being censored. [1] https://www.wired.com/story/starlink-internet-dish-hack/ https://www.wired.com/story/starlink-internet-dish-hack/ [2] https://github.com/KULeuven-COSIC/Starlink-FI https://github.com/KULeuven-COSIC/Starlink-FI

gorkish 4y ago
This bothered me yesterday when news broke. I'm surprised that more people are not discussing the lack of follow-on information here.
upupandup 4y ago
- samstave 4y ago
- roastedpeacock 4y ago
  > looks like Starlinks legal dept got to the github repo first :( If true than it was not through the normal DMCA process of GitHub that would result in a public[1] take-down notice being filed for transparency. [1] https://github.com/github/dmca https://github.com/github/dmca
jacooper 4y ago
Should've uploaded the repo to IPFS or Radicle.
colinsane 4y ago
archive.org only ever captured 404s for that page. i wonder if it was a typo in the article. does Starlink use TI’s SimpleLink? because there’s a very similarly-named repo doing similar fault injection here: https://github.com/KULeuven-COSIC/SimpleLink-FI https://github.com/KULeuven-COSIC/SimpleLink-FI
- roastedpeacock 4y ago
  Wondered that too but the presentation slides make no mention of anything related to SimpleLink. Than again there could be more under the hood than just what the slides themselves describe. Close but probably not a match.
no-dr-onboard 4y ago
DEF CON goon here. Sometimes our presenters provide the link to a private GitHub repo to the press in advance of their presentation. After the presentation they make the repo public.
- roastedpeacock 4y ago
  :-) Might be better to encourage placeholder repository to avoid concerns from the public such as this but as long as the presenter ultimately controls the namespace it is not really at issue.
  - sneak 4y ago
    Microsoft and the US military ultimately controls the namespace on GitHub.com.
    - bee_rider 4y ago
      What's the relationship between the US military and github?
      - sneak 4y ago
        They get to dictate to Microsoft what is and isn’t allowed on github.com. Microsoft will not fight a 1A battle against one of their biggest and oldest partners. Not only are they one of their largest customers, they have physical control over the place where Microsoft and GitHub staff live and work.
        awwaiid 4y ago
        ... you mean the US, possibly allies? Not only is that broad enough to be meaningless, I don't know offhand of any military going to someone's house to require them (by force I assume) to change their GitHub repo name. What are you getting at?
        4y ago
roastedpeacock 4y ago
Repository is live now. Commit cbde04c9bc45ea54cc509a65247c62a82f64bca9 From README > We are not providing exact glitch parameters. The presentation slides contain various hints and the parameters will vary depending on how you patch the firmware. Some may see this as capitulation towards Starlink business interests but a more benign reason could involve the glitch parameters varying based on various hardware factors and as stated the execution of firmware as well.

gorkish 4y ago

This bothered me yesterday when news broke. I'm surprised that more people are not discussing the lack of follow-on information here.

upupandup 4y ago

samstave 4y ago
roastedpeacock 4y ago
> looks like Starlinks legal dept got to the github repo first :( If true than it was not through the normal DMCA process of GitHub that would result in a public[1] take-down notice being filed for transparency. [1] https://github.com/github/dmca https://github.com/github/dmca

jacooper 4y ago

Should've uploaded the repo to IPFS or Radicle.

colinsane 4y ago

archive.org only ever captured 404s for that page. i wonder if it was a typo in the article. does Starlink use TI’s SimpleLink? because there’s a very similarly-named repo doing similar fault injection here: https://github.com/KULeuven-COSIC/SimpleLink-FI https://github.com/KULeuven-COSIC/SimpleLink-FI

roastedpeacock 4y ago
Wondered that too but the presentation slides make no mention of anything related to SimpleLink. Than again there could be more under the hood than just what the slides themselves describe. Close but probably not a match.

no-dr-onboard 4y ago

DEF CON goon here. Sometimes our presenters provide the link to a private GitHub repo to the press in advance of their presentation. After the presentation they make the repo public.

roastedpeacock 4y ago
:-) Might be better to encourage placeholder repository to avoid concerns from the public such as this but as long as the presenter ultimately controls the namespace it is not really at issue.
- sneak 4y ago
  Microsoft and the US military ultimately controls the namespace on GitHub.com.
  - bee_rider 4y ago
    What's the relationship between the US military and github?
    - sneak 4y ago
      They get to dictate to Microsoft what is and isn’t allowed on github.com. Microsoft will not fight a 1A battle against one of their biggest and oldest partners. Not only are they one of their largest customers, they have physical control over the place where Microsoft and GitHub staff live and work.
      - awwaiid 4y ago
        ... you mean the US, possibly allies? Not only is that broad enough to be meaningless, I don't know offhand of any military going to someone's house to require them (by force I assume) to change their GitHub repo name. What are you getting at?
        4y ago

roastedpeacock 4y ago

Repository is live now. Commit cbde04c9bc45ea54cc509a65247c62a82f64bca9 From README > We are not providing exact glitch parameters. The presentation slides contain various hints and the parameters will vary depending on how you patch the firmware. Some may see this as capitulation towards Starlink business interests but a more benign reason could involve the glitch parameters varying based on various hardware factors and as stated the execution of firmware as well.