Bug 1420327
| Summary: | CURL 7.29 cannot connect to FTPS using proxytunnel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | dbodnarc |
| Component: | curl | Assignee: | Kamil Dudka <kdudka> |
| Status: | CLOSED ERRATA | QA Contact: | Karel Srot <ksrot> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | dbodnarc, kdudka |
| Target Milestone: | rc | Keywords: | Patch |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | curl-7.29.0-42.el7 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 17:02:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
dbodnarc
2017-02-08 13:14:04 UTC
Thank you for reporting the bug! I am able to reproduce it locally and will find the cause. This seems to be broken by the following upstream commit: https://github.com/curl/curl/commit/curl-7_29_0~91 We need to fix the code such that the CONNECT phase blocks. I have pushed a patch upstream to fix this bug: https://github.com/curl/curl/commit/curl-7_52_1-124-g8fa5409 It should be easy and safe to backport for RHEL-7 curl. Thank you for providing the additional info! I am able to reproduce it locally and I will fix it by applying the following upstream commits: https://github.com/curl/curl/commit/curl-7_37_1-19-ga4cece3 https://github.com/curl/curl/commit/curl-7_43_0-4-gb88f980 Note that the above commits fix the logic at HTTP level while the original fix for this bug fixes the TLS backend of libcurl. Could you please verify that curl-7.29.0-40.el7 works as expected? Ooops, still not perfect. It seems to hang in certain situations. This will need some additional debugging... Additional commit pushed upstream: https://github.com/curl/curl/commit/curl-7_53_1-120-g2549831 Still debugging... One more commit needs to be picked from upstream: https://github.com/curl/curl/commit/curl-7_33_0-60-gd44b014 Could you please verify that curl-7.29.0-42.el7 works as expected? I've checked the latest curl-7.29.0-42.el7 and it works fine for me now thank you. Perfect. Thanks for confirmation! Just FYI, when following the reproducer I have encountered that when using -proxytunnel parameter curl seem to work but it is complaining with: Warning: Invalid character is found in given range. A specified range MUST Warning: have only digits in 'start'-'stop'. The server's response to this Warning: request is uncertain. The right approach is to specify the option as --proxytunnel. (In reply to Karel Srot from comment #29) > Just FYI, when following the reproducer I have encountered that when using > -proxytunnel parameter curl seem to work but it is complaining with: > > Warning: Invalid character is found in given range. A specified range MUST > Warning: have only digits in 'start'-'stop'. The server's response to this > Warning: request is uncertain. This was caused by "-proxytunnel" being interpreted as URL containing a glob. The glob parser can be disabled by the --globoff (-g) option of curl. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2016 |