DNS Leak with FTP redirect or FTP URL with Sock5 [40288136]

Duplicate

of 40146706

Bug

Status Update

No update yet.

Description

ch...@cotehome.com

created issue #1

Sep 17, 2012 11:27PM

Chrome Version : 21.0.1180.89
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:

What steps will reproduce the problem?
below assumes you have a working secure socks 5 setup.

type ftp://www.news.com
OR
type ftp.news.com
watch Wireshark pole local DNS

What is the expected result?
Traffic *should* be blocked! Since traffic is tunneled through sock5. This does not happen however.

What happens instead?
local dns was polled

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1

Comments

ph...@chromium.org <ph...@chromium.org> #2Oct 9, 2012 08:21AM

[Empty comment from Monorail migration]

cb...@chromium.org <cb...@chromium.org> #3Oct 11, 2012 08:38PM

Thanks for the bug - and sorry that it went undiscovered for a little bit.

I took a quick look at our SOCKS5 support and we seem to be doing the CONNECT with a domain name [SOCKS5 also allows the client to do the resolution and provide an IPv4 or v6 address].

It might help to get a net-internals dump. See

http://dev.chromium.org/for-testers/providing-network-details for details.

I'll also try to repro myself.

er...@chromium.org <er...@chromium.org> #4Oct 12, 2012 01:12AM

There is no proxy support for FTP

ch...@cotehome.com <ch...@cotehome.com> #5Oct 12, 2012 01:27AM

Great, that clarifies FTP support. Which I have no use for and many others. So if there is no proxy support for FTP, then WHY is it leaking DNS outside of the proxy for something that is not supported? DNS does not mean FTP.

The DNS lookup should happen over proxy.
The FTP request should be blocked if it's not supported.

er...@chromium.org <er...@chromium.org> #6Oct 12, 2012 01:29AM

Status: Duplicate of

40146706

See

https://crbug.com/chromium/11227. Configuring a proxy for FTP has no effect in Chrome. The request is not being sent through the proxy.

bu...@chromium.org <bu...@chromium.org> #7Mar 10, 2013 09:06PM

[Empty comment from Monorail migration]

er...@chromium.org <er...@chromium.org> #8Aug 28, 2020 09:59PM

[Empty comment from Monorail migration]

[Monorail components: Internals>Network]

is...@google.com <is...@google.com> #9Aug 28, 2020 09:59PM

This issue was migrated from

crbug.com/chromium/150027?no_tracker_redirect=1

[Auto-CCs applied]
[Multiple monorail components: Internals, Internals>Network, Internals>Network>DNS, Internals>Network>FTP, Internals>Network>Proxy]
[Monorail mergedinto:

crbug.com/chromium/11227]
[Monorail components added to Component Tags custom field.]