I'd like to mention a specific case where the Android scheme fails
catastrophically: Lots of apps ask for permission to "modify and delete
USB storage contents" (that's from memory, the exact phrase may be
different). This _sounds_ really scary, and it is: IIUC apps with that
privilege _could_
Jonas,
Thanks for taking the time to document your thoughts. I also caught up with
Chris Jones from B2G yesterday to go security, and we discussed app permissions
as well. I have written up a couple pages of notes, but I'd like to a key
difference. From our discussion yesterday (and Chris corre
Mark and I were talking about a related issue, and I thought it might be
helpful to track taint for content copied to the clipboard and raise a
warning if the user attempts to paste it into a context where Javascript
code might get executed (for example, the address bar, or the web
developer toolba
Hello Adrienne -
Thanks for the good thoughts. I think we all 100% agree that installation
time is the wrong time to ask. I'm wondering about your thoughts on asking for
all permissions at the same time (in a list, with the option to selectively
allow different permissions) or as they are us
Hi Jonas,
Thank you for sending this out! I really like the model overall.
With sensitive APIs, even if a 3d party vouches for the capabilities of the
app, I believe we would still want to communicate that to the user somehow at
installation time? I'm concerned we'd end up with a pretty lon
To be clear, the feature page currently proposes to implement a minimal,
universal click to play for all plugins as the initial phase. That gives us
some time to figure out the long term strategy.
Lucas.
On Mar 6, 2012, at 11:31 PM, Lucas Adamski wrote:
> Hi all,
>
> Thank you for the thou
