3 ms·
Here's a description of what we've done to solve that problem: https://www.airbornos.com/docs/security https://www.airbornos.com/docs/security
by twiss 9y ago
Here's a description of what we've done to solve that problem: https://www.airbornos.com/docs/security https://www.airbornos.com/docs/security
- EGreg 9y agoThat's interesting, but you're plugging holes in a waterfall I think. For example, that first visit which installs the service worker can already deliver bad code. Not saying you will do it, but it all relies on people trusting you not to do it. So statements like "we CAN'T read your stuff" are not true on the web. Luckily, most web users don't care about being hacked by the server - they care about owning their own data! :)
- twiss 9y ago> For example, that first visit which installs the service worker can already deliver bad code. Yes, but that is also the case when you install a desktop app. That's why Airborn OS is open source, so that you can inspect the code.
- EGreg 9y agoAgreed but with a desktop app, the author can sign it and the OS verifies that signature. Sadly the Web does no such thing with the top level document.
- twiss 9y agoYes, that's true, but the author (or intermediary-who-delivers-the-binary) can also.. not sign it (deliver an unsigned version). Often, you don't have many other options than to trust the binary the website is serving you.
- jimktrains2 9y agoIt also happens far less frequently and I can do it at my leisure, or even just compile it on my own.