Bug 8324: Prevent DNS proxy bypasses caused by Drag&Drop
Try to keep a good level of protection against leaks caused by accidental link drags, while not hampering usability (e.g. bookmarks reordering or intentional navigation gestures):
- Keep the torbutton!106 (merged) fix against
text/plain
andtext/html
fallback flavors escaping the filter - Limit the protection to actual links (i.e. anchor elements or other DOM elements which cause a
text/x-moz-url
data flavor to be added to the transferable object) as it was originally meant - Drop any attempt to guess "selected text containing URLs"
- Explicitly exempt bookmarks
- Allow as much as possible dragging links onto the Tor Browser's own UI, for navigation and bookmarking purposes
Part of #41518, fixes #41520 (closed).
Merge request reports
Activity
assigned to @ma1
mentioned in merge request torbutton!118 (merged)
mentioned in issue #41518
requested review from @richard
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
Yes, removing
hasURLish
is a good idea.The "text/x-moz-text-internal" makes up for the most of the chrome-behaviour that would otherwise be blocked, like dragging links into the URL bar. And we can always use this to hack around other chrome behaviour we've accidentally broken. Unfortunately, it also seems to block dragging within a page.
The main consistent issue is the current code calls
getData
,clearData
andsetData
, rather than the equivalent "moz" that accept the list index. This means that we're only editing the first item in the data transfer.added 1 commit
- 64d8a413 - Bug 41518: Drag&Drop protection improvements
added 1 commit
- 690e4983 - Bug 41518: Drag&Drop protection improvements
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
added 1 commit
- 2e46b6a9 - Bug 41518: Drag&Drop protection improvements
added 1 commit
- c2d33abf - Bug 41518: Drag&Drop protection improvements
- Resolved by Pier Angelo Vendrame
Not a fan of "Bug 41518: Drag&Drop protection improvements" as a commit subject.
I think we should
- create a fixup! that removes the drag and drop protection from torbutton
- find out the original Drag&Drop protection (edit: good candidates are either legacy/trac#8324 (closed) or #10716 (closed)
). - move all the implementation to a commit that starts with "Bug 8324: Prevent DNS proxy bypasses caused by Drag&Drop". This can be in
toolkit/torbutton
for starters, but ideally we would move it insidebrowser/something
.
Edited by Pier Angelo Vendrame
- Resolved by ma1
- Resolved by ma1
- Resolved by ma1
Looks good. @ma1 I'm assuming this commit is temporary until "drag and drop protection" is split out from "Bug 10760: Integrate TorButton to TorBrowser core" into its own commit, and this would be merged into it?
Or do you want to do what was suggested in !481 (4e9f1b9c, comment 2862455) now?
marked this merge request as draft from ma1/tor-browser@3252f518
added 11 commits
-
45909fc0...fdfd2b97 - 9 commits from branch
tpo/applications:tor-browser-102.5.0esr-12.5-1
- d84fac57 - fixup! Bug 10760: Integrate TorButton to TorBrowser core
- a1ee91a6 - Bug 8324: Prevent DNS proxy bypasses caused by Drag&Drop
-
45909fc0...fdfd2b97 - 9 commits from branch
marked this merge request as draft from ma1/tor-browser@d84fac57