Bug#810933: Please support connecting to SMTP via a SOCKS proxy
Package: reportbug
Version: 12.0.0
Followup-For: Bug #810933
(Note: I'm not on Debian but on a derivative with the same issue)
I use tsocks as a workaround, however this causes reportbug to fail checking for newer versions and other bug reports:
~$ tsocks reportbug -d
Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you don't know what package the bug is in, please contact debian-
user@lists.debian.org for assistance.
> reportbug
Is "reportbug" actually the package you are having problems with [Y|n|q|?]?
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Bug reporter xyz <mxuser1234@morke.org>' as your from address.
Getting status for reportbug...
Checking for newer versions at madison...
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on reportbug src:reportbug...
Error retrieving information on existing bug reports from the BTS. The following error was detected:
Unable to connect to Debian BTS (error: "TimeoutError('timed out')");
Do you still want to file a report [y|N|q|?]? n
Firewall logs in dmesg and netstat both show that reportbug successfully connects to the proxy server (I micromanage loopback connections...):
tcp 0 0 127.0.0.1:39016 127.0.0.1:9050 ESTABLISHED 324914/python3
I have verified:
1. My DNS server works and reportbug can use it (that DNS leak should be addressed btw, maybe add socks5 protocol support?)
2. My Proxy server works and has access to the internet
3. My Proxy's IP address is not blacklisted or else the workaround below would not work
Workaround:
1. Set a custom http proxy when creating the bug report (I use privoxy):
reportbug --proxy http://127.0.0.1:8118
2. Go through the steps, create bug report
3. Don't send bug report, quit reportbug
4. Resume bug reporting using tsocks:
tsocks reportbug -r /tmp/reportbug-reportbug-[...]
5. Send bug report; drink tea
I have verified:
tsocks is set up correctly, all data is proxified, no direct internet access permitted or attempted (except for the DNS lookup which I proxy too).
-- Package-specific info:
** Environment settings:
INTERFACE="text"
** /home/vulnerablenet/.reportbugrc:
reportbug_version "12.0.0"
mode novice
ui text
realname "Bug reporter xyz"
email "mxuser1234@morke.org"
no-cc
smtphost reportbug.debian.org
-- System Information:
Debian Release: 12.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages reportbug depends on:
ii apt 2.6.1
ii python3 3.11.2-1+b1
ii python3-reportbug 12.0.0
ii sensible-utils 0.0.17+nmu1
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
ii debconf 1.5.82
pn debsums <none>
pn default-mta | postfix | exim4 | mail-transport-agent <none>
pn dlocate <none>
pn emacs-bin-common <none>
ii file 1:5.44-3
ii gnupg 2.2.40-1.1
pn python3-urwid <none>
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt 2.6.1
ii file 1:5.44-3
ii python3 3.11.2-1+b1
ii python3-apt 2.6.0
ii python3-debian 0.1.49
ii python3-debianbts 4.0.1
ii python3-requests 2.28.1+dfsg-1
ii sensible-utils 0.0.17+nmu1
python3-reportbug suggests no packages.
-- no debconf information
Reply to: