4 ms·
Honest question: but what’s the threat model for wanting an OS to block this? I’ve so far only thought of leaking IP address and Bitcoin mining. But any website
by manwe150 7y ago
Honest question: but what’s the threat model for wanting an OS to block this? I’ve so far only thought of leaking IP address and Bitcoin mining. But any website already easily has both capabilities (with somewhat arbitrary open sockets after the WebSockets handshake). Is the expectation that an app implementation should have less permissions than an equivalent website and so be the “safer” option?
- hrktb 7y agoIsn’t it the same as any other access permission ? For instance is there any specific model behind blocking device location, short of just not wanting to share the info ? I’d see not wanting an app to send anything related to your device nor that it was even opened to be of the same kind.
- SpicyLemonZest 7y agoI want to ensure that the app is just locally computing the decibel level, rather than streaming out data about what it's hearing. I would ideally want websites to also have a "no more network access after your initial load" mode, but as you say that's fundamentally incompatible with modern web development. So I kinda just accept the loss there.