If I recall, for something like GPON or XGS-PON, you end up having to clone the various attributes of the original for it to work properly. This typically includes serial number, hardware id, firmware identifiers, etc.
For most it is just serial number. The 8311 folks have scripts that will fully automate the cloning for most common devices. This is not like a "break open your hardware and attach wires" type thing.
There are some ISPs issuing and verifying certs for GPON, which are more annoying to extract. I'm not aware of anyone (even those same ISPs) doing it for XGS-PON. It seems they all decided maintainimg their own CA infrastructure for millions of customers was not worth it ;)
Question out of curiosity. I once swapped a TPLink media converter between two homes, both using the same ISP, to debug internet issues and to see if that would improve the situation. Did I do something incredibly illegal? And did my ISP get confused seeing my media converter on the other side of town?
When I was a kid I used to pack my house's cable modem in a backback and bring it to my friend's house a couple miles away when I'd visit to play Xbox Live. My dad had a back-up dial-up connection for emails and mom didn't use the internet very much so usually wouldn't mind unless he needed to work. I remember this working at greater distances in other places occasionally too.
Earlier, in the dial-up era, my dad didn't feel like paying for internet at home and work, so after school I would call his office and ask his secretary if he had left for his evening meetings yet. If so, she'd disconnect his dial-up connection and I'd get a couple hours to myself after school.
We didn't have two phone lines at home so I'm not sure what happened if he needed it unexpectedly. I think he also had a by-the-minute service as a backup or maybe his partner in the office had a separate plan? This was all done under agreed rules I only vaguely remember so must not have been a frequent problem.
Always funny to think back to that era when internet wasn't assumed to be a 24/7 thing and losing internet for a day wasn't the end of the world...
This wouldn't be criminally illegal anywhere unless done with some sort of fraudulent intent, but maybe in some places the ISP could make you swap them back.
Qualcomm kind of does this with their XPAN extension, sends the audio over local network. I believe it's mostly a proprietary solution though, so I haven't seen any serious attempts to re-implement it yet.
> Most vendors gave the security researchers either silent treatment or were slow, even after Airoha published fixes. Jabra was one of the positive outlier, Sony unfortunately negatively.
While I don't recall Sony issuing an advisory, I believe the users of their app would have started getting update notifications since they (quietly) released firmware updates.
> This means there is great opportunity for Linux users to control their Bluetooth headsets, which for example is quite nice in an office setting to toggle "hearthrough" when toggling volume "mute" on your machine.
I think most vendors are using custom services with their own UUIDs for settings such as this.
Regardless, I believe there are open client implementations for some of the more popular devices. Gadgetbridge comes to mind in regards to Android, not sure about any Linux equivalent.
It did a great deal more than that. It also allowed the toggling of VoNR, which apparently affected the fallback behavior of some people's services. (Ie. It would fall back to LTE and not roam back to 5G data unless nudged manually)
However for me, it would enable backup calls over a secondary sim card's data, which would allow text and calls overseas without the usual extortionate charges. Oddly enough, I believe that toggle is enabled for my carrier... but only on iOS.
The part that does not work on iOS is putting SIM2 into airplane mode so that it can do VoWiFi without connecting to the network. That would reduce power consumption and avoid utterly obnoxious behavior on the part of some carriers (cough, Visible).
The major carriers perhaps, but support among the MVNOs isn't universal. Number sharing support for smart watch usage is almost non-existent among the MVNOs in Australia.
Eg. ALDI (yes, the German supermarket chain run a MVNO in Australia), have been saying esim support in the future since 2021.
They've pulled out of my market (Australia) 6 years ago, so that's not really an option, even if I imported one.
If I imported one, the majority of the handsets released before this year wouldn't be able to register on a network, given that the networks have gone and blocked the IMEI TAC associated with most of Sony's handsets.[1]
This is due to Sony not having the correct carrier settings in order to roam onto them for emergency calls, and a ham-fisted direction to have working emergency calls post-3G shutdown.
I loved the early Sony Ericsson but they lost their way on the phones. And the funky camera phones when their stand alone phones are decent to cutting edge.
It's still a pretty hard question to answer, given how specific model numbers are sometimes missing on sales listings, and silent revisions to hardware.
Most likely referring to CVE-2018-6242 aka "Fusée Gelée"
The paperclip was just the easiest way of triggering RCM, which is a standard feature on Tegra. The vulnerability lay in that they didn't bounds check certain types of USB requests properly.
reply