bugGNU Wget - Bugs: bug #20809, Emitting bug-reporting info


bug #20809: Emitting bug-reporting info

Submitter:  Micah Cowan <micahcowan>
Submitted:  Fri 17 Aug 2007 11:33:40 PM UTC
Category:  Feature Request Severity:  3 - Normal
Priority:  4 Status:  Confirmed
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  None Operating System:  None
Reproducibility:  None Fixed Release:  None
Planned Release:  1.14 Regression:  None
Work Required:  1 - Days Patch Included:  None
* Mandatory Fields

Add a New Comment Rich Markup

Fri 17 Aug 2007 11:33:40 PM UTC, original submission:  

See http://www.mail-archive.com/wget%40sunsite.dk/msg09963.html, where Tony Lewis proposes a --bug option. However, my opinion is that most of this functionality can and should be rolled into the current --debug option; it seems to me that the primary purpose of the --debug option is to give as much information as possible, and often for the purpose of sharing with other users; whether knowledgeable friends, the bug tracker, or the Wget mailing list.

Users need a way to ask Wget to emit output suitable for inclusion in a bug report/support request. In particular, this mode should prevent Wget from emitting password info to output by default.

The idea is that wget should substitute some harmless string for the argument to PASS, in URIs that include "user:pass@" authentication info, in the Authorization and Proxy-Authentication HTTP headers when Basic mechanism is used.

It's unclear whether the Authorization header should be obfuscated when Digest or similar methods are being used; perhaps we should do that as well, to be safe, as the combination of knowing what the nonce is, and what the digest value is, could allow an attacker to brute-force simple passwords.

Other ideas Tony submitted were that it would spit out the command line and rc settings, which are currently left out by debug; and allowing the user to specify a file to which this output is copied (but the info can still appear on the terminal as well).

If we include source-file-specific revision information in the wget binary, we'd probably also want to include that.

The password-obfuscating bit, wrt HTTP headers, at least, would require some reworking of how we do HTTP headers. We'd probably want to keep and emit a list of "headers-to-emit", rather than appending stuff to a buffer we'll be sending, and include the ability to flag specific headers as needing obfuscation, so we submit one version to the server, and another version to the user in our debug output.

Micah Cowan <micahcowan>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by micahcowan (Submitted the item)

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-08-21 micahcowan Planned Release1.12 1.14
    2008-04-22 micahcowan Work RequiredNone 1 - Days
    2008-01-27 micahcowan Priority5 - Normal 4
        Planned Release1.15 1.12

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code