Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!
Control: tag -1 = confirmed Hi Andy, Andrew Valencia wrote: More research... http proxying seems to be working fine. Not for me. I can reproduce this issue easily. I notice that you specify an HTTP proxy, but go out using HTTPS. Yes, but * according to the man page there is no https_proxy variable, * http_proxy should work for https as well as I read it, * it doesn't work with the mentioned host but http instead of https for me either. Can you do a straight HTTP connection and verify that it's being proxied as expected? I tried and it didn't for me, at least not on jessie where the report IIRC was written. I've now tried to following on Sid: env http_proxy=http://localhost:8118/ lynx http://torstatus.blutmagie.de/ It says: You are not using Tor You do not appear to be using Tor What I also noticed: telnet localhost 8118 works as well as telnet ::1 8118 works, but telnet 127.0.0.1 8118 does not work: Connection refused Any chance that lynx only supports HTTP proxies on IPv4 and silently ignores the proxy if it doesn't work? That would explain the two different findings once by the original reported and me (who can reproduce the issue) and once by Andy who can't reproduce it. Andy: Have you tried it with Tor as proxy on port 8118 as reported or with a different proxy? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!
[Axel Beckert a...@debian.org writes:] * according to the man page there is no https_proxy variable, * http_proxy should work for https as well as I read it, * it doesn't work with the mentioned host but http instead of https for me either. I read lynx as thinking of the world as proto://path Thus, when proto is https, they expect https_proxy. (My thinking may be polluted by having read some of the proxy handling code in Lynx src.) Oh, yeah, also in the source: LYrcFile.h:#define RC_HTTPS_PROXY https_proxy LYrcFile.h:#define RC_HTTP_PROXY http_proxy Distinct. telnet localhost 8118 works as well as telnet ::1 8118 works, but telnet 127.0.0.1 8118 does not work: Connection refused I tested with tinyproxy, in an all-IPv4 network (residue of some bad regressions a while back in various apps, I'll have to revisit some day soon). I have two Internet feeds, and my host goes out one and I set the proxy to go out the other. So then I can visit a page on an external web server of mine and see from the logs what client IP address was involved. It definitely works in this basic configuration. So I try two versions. My dev build (for -g symbols): Lynx Version 2.8.8rel.2 (09 Mar 2014) and Wheezy repo: Lynx Version 2.8.8dev.12 (22 Feb 2012) Both work, with verification in the logs that the proxy is used when http_proxy is set. I'm not well set up to test IPv6 aspects; if you don't have time I'll have to put together a lab network which will be later this week. Let me know and I'll put it on the calendar. Also, if there's some other Lynx version in play, point me at it and I'll test. Finally(!), haven't heard from the submitter. Should I try and ping his email directly? What's the usual practice? Thanks, Andy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!
Code inspection leads me to LYUtils.c, routine is_url(), which calls LYCheckForProxyURL() only if the URL type is not known. HTTP, of course, is known--thus it quietly ignores the proxy environment variable config. If another dev has a proxy server ready to go, an interesting experiment would be to move the proxy test to be done first in is_url(). But don't be surprised if what you find is that this bug needs to be renamed HTTP proxy is broken. I'll try and set up a proxy server RSN if nobody else is jumping on this. Andy Valencia On 7/4/15, Nomen Nescio nob...@dizum.com wrote: Package: lynx Version: 2.8.9dev1-2 Severity: important Dear Maintainer, The http_proxy variable is silently ignored! ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791452: [pkg-lynx-maint] Bug#791452: lynx: http_proxy variable silently ignored!
More research... http proxying seems to be working fine. I notice that you specify an HTTP proxy, but go out using HTTPS. Can you try using an HTTPS proxy (sometimes problematic, I know)? Can you do a straight HTTP connection and verify that it's being proxied as expected? On 7/5/15, Andrew Valencia lynxoma...@gmail.com wrote: Code inspection leads me to LYUtils.c, routine is_url(), which calls LYCheckForProxyURL() only if the URL type is not known. HTTP, of course, is known--thus it quietly ignores the proxy environment variable config. If another dev has a proxy server ready to go, an interesting experiment would be to move the proxy test to be done first in is_url(). But don't be surprised if what you find is that this bug needs to be renamed HTTP proxy is broken. I'll try and set up a proxy server RSN if nobody else is jumping on this. Andy Valencia On 7/4/15, Nomen Nescio nob...@dizum.com wrote: Package: lynx Version: 2.8.9dev1-2 Severity: important Dear Maintainer, The http_proxy variable is silently ignored! ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791452: lynx: http_proxy variable silently ignored!
Package: lynx Version: 2.8.9dev1-2 Severity: important Dear Maintainer, The http_proxy variable is silently ignored! This is very dangerous, because a privoxy/tor user who relies on this setting for privacy will be compromised, and they generally will not even be aware of the compromise because the browser retrieves pages over an untrusted connection without warning. For example, suppose a tor user configures privoxy on port 8118. This will yield an exposed session: $ export http_proxy=http://localhost:8118 $ lynx To prove that this bug exists, a tor user can run: $ http_proxy=http://127.0.0.1:8118 lynx https://torstatus.blutmagie.de/ and see the message saying that the connection is not from the tor network. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lynx depends on: ii lynx-cur 2.8.9dev1-2+b1 lynx recommends no packages. lynx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
