You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a minor privacy issue in distinguishing between "no apps are available" and "the user cancelled the share"; if only a handful of popular targets exist for a particular payload (especially if we add new share types that might have specialized handlers, e.g., for rare MIME types) then a malicious site could use navigator.share to check whether those apps are installed, based on the response string.
Also, in our current Android implementation, we are totally unable to distinguish between "no apps are available" and "the user cancelled the share". Therefore, let's just remove this provision. I won't go as far as to explicitly bar the user agent from distinguishing these, but add a note under security considerations.
The text was updated successfully, but these errors were encountered:
mgiuca
added a commit
to mgiuca/web-share
that referenced
this issue
Jun 2, 2017
Added a security consideration that implementations should be careful
about exposing this information.
This isn't a technical change, but changes a weak recommendation *to*
differentiate error cases to a weak recommendation *against* it.
Closesw3c#29.
Added a security consideration that implementations should be careful
about exposing this information.
This isn't a technical change, but changes a weak recommendation *to*
differentiate error cases to a weak recommendation *against* it.
Closesw3c#29.
Raised by @dbaron on the TAG review.
There is a minor privacy issue in distinguishing between "no apps are available" and "the user cancelled the share"; if only a handful of popular targets exist for a particular payload (especially if we add new share types that might have specialized handlers, e.g., for rare MIME types) then a malicious site could use
navigator.share
to check whether those apps are installed, based on the response string.Also, in our current Android implementation, we are totally unable to distinguish between "no apps are available" and "the user cancelled the share". Therefore, let's just remove this provision. I won't go as far as to explicitly bar the user agent from distinguishing these, but add a note under security considerations.
The text was updated successfully, but these errors were encountered: