Changes between Initial Version and Version 1 of Ticket #18101, comment 62


Ignore:
Timestamp:
Nov 9, 2017, 7:14:16 PM (19 months ago)
Author:
arthuredelstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18101, comment 62

    initial v1  
    44I was able to reproduce this on Windows 7, but not on Windows 8 Server or Windows 10.
    55
    6 To attempt to fix this on Windows 7, I tried using both IFileDialog and GetOpenFileName. Both show the same modern file dialog. It's possible to hook some UI events in both, using IFileDialogEvents and OPENFILENAME.lpfnHook respectively. But, unfortunately, there is no event that occurs after the user clicks the "Open" button (or presses enter), and before the DNS leak occurs, that could allow us to cancel the event and prevent the leak.
     6To attempt to fix this on Windows 7, I tried using both IFileDialog and GetOpenFileName. Both show the same modern file dialog. It's possible to hook some UI events in both, using IFileDialogEvents and OPENFILENAME.lpfnHook respectively. But, unfortunately, there is no event that occurs after the user clicks the "Open" button (or presses enter), and before the DNS leak occurs, that could allow us to cancel the event and prevent the leak. Here's the code I used for experimentation: https://gist.github.com/arthuredelstein/eaad2bc94e4836dad831ed7213fbcfe3
    77
    88As an experiment, I tried using the Windows Firewall to block internet connections from firefox.exe. While browsing the web is blocked as expected, the file dialog still causes DNS leaks! So it seems the leak may be happening outside the browser process.