Cyberduck Mountain Duck CLI

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#8733 closed defect (fixed)

Should not try to resolve address when connecting through HTTP proxy

Reported by: brian.w.walker@… Owned by: dkocher
Priority: high Milestone: 4.7
Component: s3 Version: 4.6.5
Severity: major Keywords:
Cc: Architecture: Intel
Platform: Windows 7

Description

We are trying to use Cyberduck to connect to an S3 compatible provider via our Proxy solution. We set the settings to use system proxy and put in all the information for the connection. We use our proxy to do DNS resolution for external URL's and not our internal DNS servers. When we try and connect to the S3 bucket we get a DNS resolution error that is cannot resolve the DNS name for the Storage URL on the internet. I think what is happening is Cyberduck is trying to get DNS from the internal DNS servers configured in the OS and not allowing the Proxy to provide the lookup. Can you provide some support on this?

Attachments (1)

Ticket 8733 - Verizon S3 Storage URL.docx (142.0 KB) - added by brian.w.walker@… 4 years ago.

Download all attachments as: .zip

Change History (20)

comment:1 Changed 4 years ago by dkocher

  • Resolution set to worksforme
  • Status changed from new to closed

A HTTP proxy server does not provide DNS resolution. Provide a DNS server IP address in TCP/IP system settings that can resolve the DNS name.

comment:2 Changed 4 years ago by brian.w.walker@…

:) Actually in our case it does. We don't allow our internal DNS servers to resolve external addresses for security reasons and all external resolution is done by our Zscaler Proxies. So the issue we are running into with Cyberduck is that Cyberduck is trying to resolve using the DNS servers set on OS and not resolution coming from Proxy. We have tested another tool called Cloudberry Explorer and that works with our proxy but does not offer a Linux version which is an issue for us. Would come one be willing to work with us to try and resolve?

comment:3 Changed 4 years ago by dkocher

Please post the system configuration proxy settings.

Changed 4 years ago by brian.w.walker@…

comment:4 Changed 4 years ago by dkocher

  • Milestone set to 4.7
  • Resolution worksforme deleted
  • Status changed from closed to reopened
  • Summary changed from DNS Resolution Issues to Should not try to resolve address when connecting through HTTP proxy

comment:5 Changed 4 years ago by dkocher

We are connecting to an S3 compatible storage bucket on Verizon. We are reaching to the internet through our Proxy and our Proxy does the DNS resolution  on traffic going out. I think what is happening is that Cyberduck is doing DNS lookups via the DNS servers set on the system (Internal) and not allowing the Proxy to provide the lookup. So when Cyberduck does the DNS request for storage-iad3a.cloud.verizon.com and uses the internal servers, it is not able to resolve. We don’t allow internal DNS servers to resolve external addresses. What we need is Cyberduck to get the DNS lookup form the Proxy on Port 80.

When connecting through the HTTP proxy the target hostname storage-iad3a.cloud.verizon.com should just be passed in the CONNECT header and not be resolved. The hostname will be resolved by the proxy and Cyberduck does no DNS lookup for the target server at all but only for the proxy.

comment:6 follow-up: Changed 4 years ago by brian.w.walker@…

Can we chat on the phone to discuss?

comment:7 Changed 4 years ago by dkocher

  • Resolution set to fixed
  • Status changed from reopened to closed

In r17294. Please update to the latest snapshot build available.

comment:8 follow-up: Changed 4 years ago by brian.w.walker@…

Is that a Linux update version as well?

comment:9 in reply to: ↑ 8 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

Is that a Linux update version as well?

Snapshot builds for Cyberduck CLI for Linux will be available within a few minutes.

comment:10 in reply to: ↑ 6 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

Can we chat on the phone to discuss?

We prefer to keep the conversation documented in this thread for future reference.

comment:11 follow-up: Changed 4 years ago by brian.w.walker@…

ok, I am running Ubuntu 14.04. I am not an ubuntu expert. Can you give me the exact commands to run to grab th new package and install?

comment:12 in reply to: ↑ 11 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

ok, I am running Ubuntu 14.04. I am not an ubuntu expert. Can you give me the exact commands to run to grab th new package and install?

Please follow our instructions to use the DEB Package Repository with the nightly source added.

comment:13 follow-up: Changed 4 years ago by brian.w.walker@…

We grabbed the new version. Can you help with Command Line for connecting to Verizon using our access and private key?

comment:14 follow-up: Changed 4 years ago by brian.w.walker@…

Will the Linux version use the proxy settings on execution, or do we need to configure the linux CLI to use the proxy?

comment:15 in reply to: ↑ 14 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

Will the Linux version use the proxy settings on execution, or do we need to configure the linux CLI to use the proxy?

Good point. Added default proxy finder implementation that should work on Linux in r17304.

comment:16 in reply to: ↑ 13 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

We grabbed the new version. Can you help with Command Line for connecting to Verizon using our access and private key?

Added help text to install connection profile for CLI version in r17305. Run duck --help. You can install the Verizon connection profiles in ~/.duck/profiles/.

comment:17 Changed 4 years ago by dkocher

An updated snapshot build (r17306) is now available.

comment:18 follow-up: Changed 4 years ago by brian.w.walker@…

Can you provide details on how to install profiles? The documentation is a little vague

comment:19 in reply to: ↑ 18 Changed 4 years ago by dkocher

Replying to brian.w.walker@…:

Can you provide details on how to install profiles? The documentation is a little vague

Is comment 16 not clear?

Note: See TracTickets for help on using tickets.
swiss made software