31–40 of 62 posts
I'm unable to get it to work with my receiver (setRegBuffer failed block=0x600 reg=74, Caused By: RadioError.UsbTransferError: USB write failed value=0x74 index=0x610 status=stall), but I love the idea! Looking forward to a local webusb+rtlsdr based Flightradar.
Do you plan on expanding the functionality? It is really amazing how flawless it work. You should do a blog post describing how you did it.
I'm unable to get it to work with my receiver (setRegBuffer failed block=0x600 reg=74, Caused By: RadioError.UsbTransferError: USB write failed value=0x74 index=0x610 status=stall), but I love the idea! Looking forward to a local webusb+rtlsdr based Flightradar.
Is your stick an RTL-SDR Blog V4? Because it looks like the failure happens when accessing a R828D tuner, which should be supported.
Earlier quoted context omitted.
Is your stick an RTL-SDR Blog V4? Because it looks like the failure happens when accessing a R828D tuner, which should be supported.
Unfortunately I don't know what device it is. Would a lsusb help?
If it is indeed not one of them, I'd be interested in getting one to test on, so I'd like to know where you got it from. Can you email me? My address is trivial to find or figure out knowing my website is https://jacobo.tarrio.org :-)
Earlier quoted context omitted.
Mozilla's position is to not implement this API due to security and privacy concerns, and I agree with them on that even though I'd really like to use this API too.
Given that it's been available in Chrome for 7 years, if there were any security and privacy concerns we should be able to point to at least one abuse of this API right?
[Ed.:] https://github.com/webusb/awesome lists applications using this API. It's 11≈14 depending on how you count. Most of them are pretty fringe, except arguably the 3 update/flash tools and maybe the Android mirror.
I'm not sure I'd expect to have seen a case of abuse here yet.
Earlier quoted context omitted.
Given that it's been available in Chrome for 7 years, if there were any security and privacy concerns we should be able to point to at least one abuse of this API right?
I'd say predicting instances of abuse of this API is tied to usage of the API, not existence of the API. I'd argue it's extremely generous to say we'd see a case of abuse after 10 deployments of this API. Can we point to at least 10 deployments of this API? [Ed.:] https://github.com/webusb/awesome lists applications using this API. It's 11≈14 depending on how you count. Most of them are pretty fringe, except arguably…
Or are you thinking only about attacks where the attackers have a genuine reason to ask for USB access? Because IMO that is going to pretty rare, and also not very interesting because in those cases the alternative is you download an executable with unlimited permissions.
But in any case it makes no difference. If the API has been available to 75% of users for 7 years, it's downright idiotic to think making it available to 77% of users will make a difference.
This is awesome, great work! Is there anywhere I can follow development on this? I'm really interested in seeing this evolve.
And you can always star it on GitHub: https://github.com/jtarrio/radioreceiver