- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Fri, 06 Feb 2015 14:46:25 +0100
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: public-webrtc@w3.org
* Harald Alvestrand wrote: >Den 06. feb. 2015 11:55, skrev Bjoern Hoehrmann: >> There are any number of ways to discourage use of this information for >> purposes other than those intended, starting with saying that it is not >> to be used for other purposes in the specification. User interaction can >> be required before sending such information (think file uploads and pop- >> up blockers), browsers could indicate when they send the addresses using >> some sort of notification so obtaining the information covertly would be >> difficult, the API could give sites the option to omit private addresses >> to avoid such notifications; sending private addresses could be disabled >> if the code is running in some iframe and not the main page. And so on >> and so forth. None of this would come with an actual loss of features. > >Who would obey these instructions? >Remember that we're assuming that the browsers run Javascript written by >the attacker, so we can't depend on the Javascript specification. If you are referring to the first point then most notable "attackers" are subject to social controls like bad press and regulatory entities, which work much better than the proposed "do nothing" alternative. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 · http://www.bjoernsworld.de Available for hire in Berlin (early 2015) · http://www.websitedev.de/
Received on Friday, 6 February 2015 13:46:57 UTC