--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: reportbug: Paranoid mode shows base64 instead of human readible text
- From: anonymous coward <debbug.reportbug@sideload.33mail.com>
- Date: Mon, 25 Jul 2022 10:38:10 +0200
- Message-id: <165873828975.54044.5879171279091879222.reportbug@cypher>
Package: reportbug
Version: 7.10.3+deb11u1
Severity: wishlist
Tags: a11y
X-Debbugs-Cc: debbug.reportbug@sideload.33mail.com
Using the --paranoid option shows the text of the bug report before
transmission. In my case, the body is usually base64 encoded, which
means only the headers are readible to a human.
There may be some debugging or academic merit to showing the base64,
but this is not generally what the user is interested in. This can be
improved in a couple ways:
1) After the headers, instead of showing multiple screens full of
base64, just print 1 line like:
«115 lines of base64-encoded text»
and follow that with:
[decoded body]
…
…
«OR»
2) show just the decoded msg, but give an extra option in the prompt
to show the verbatim raw msg for those who are interested.
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reportbug depends on:
ii apt 2.2.4
ii python3 3.9.2-3
ii python3-reportbug 7.10.3+deb11u1
ii sensible-utils 0.0.14
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
pn debsums <none>
pn dlocate <none>
ii emacs-bin-common 1:27.1+1-3.1
ii file 1:5.39-3
ii gnupg 2.2.27-2+deb11u2
ii postfix [mail-transport-agent] 3.5.13-0+deb11u1
ii python3-urwid 2.1.2-1
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-4.1
Versions of packages python3-reportbug depends on:
ii apt 2.2.4
ii file 1:5.39-3
ii python3 3.9.2-3
ii python3-apt 2.2.1
ii python3-debian 0.1.39
ii python3-debianbts 3.1.0
ii python3-requests 2.25.1+dfsg-2
ii sensible-utils 0.0.14
python3-reportbug suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: anonymous coward <debbug.reportbug@sideload.33mail.com>, 1016009-done@bugs.debian.org
- Subject: Re: Bug#1016009: reportbug: Paranoid mode shows base64 instead of human readible text
- From: Nis Martensen <nis.martensen@web.de>
- Date: Sun, 27 Nov 2022 11:07:34 +0100
- Message-id: <add415b9-8248-3ae3-b2d6-eae6588f9270@web.de>
- In-reply-to: <165873828975.54044.5879171279091879222.reportbug@cypher>
- References: <165873828975.54044.5879171279091879222.reportbug@cypher>
> Using the --paranoid option shows the text of the bug report before
> transmission. In my case, the body is usually base64 encoded, which
> means only the headers are readible to a human.
The point of the --paranoid option is to show text of the bug report
exactly as it would be passed to your MTA. It does not have to be human
readable for this.
> There may be some debugging or academic merit to showing the base64,
> but this is not generally what the user is interested in.
If they are not interested in this then they don't need to use the
option. The option is deliberately named "--paranoid" and disabled by
default.
If you want to check the human-readable message text before submission,
there are already menu entries to print the message to stdout or view it
in a pager. You don't need the --paranoid option for this.
Closing.
--- End Message ---