4 ms·
>A properly designed Web wrapper uses techniques to avoid this risk: filtering urls to stay in the app's domain So you are saying the WebView on Android is uns
by anon1385 12y ago
>A properly designed Web wrapper uses techniques to avoid this risk: filtering urls to stay in the app's domain
So you are saying the WebView on Android is unsafe to use for rendering untrusted content. That's a pretty serious limitation and certainly not made clear in the documentation[1]. Infact the first line of the docs suggest that a WebView is suitable to "roll your own web browser" with…
Something is seriously wrong with Google's attitude to security if they are happy to document a class that's totally unsafe for use with untrusted data as being safe. Knowing this is enough to put me off ever using Android again to be honest.
https://developer.android.com/reference/android/webkit/WebView.html https://developer.android.com/reference/android/webkit/WebVi...
- Zigurd 12y ago> That's a pretty serious limitation and certainly not made clear in the documentation Having engineered Web wrappers for a few clients, I would not have let them out the door without url filtering, and not just for security. A wild url could mess up the UX way before it becomes a security issue. Any sane "kiosk" style software should behave that way. As for the documentation, when it was written, those statements were true. Now, with Chrome implementing WebView, that documentation is once more true. And I would STILL include url filtering in a Web wrapper.