Security Considerations (GNU Wget 1.21.1-dirty Manual)
From Get docs
Wget/docs/latest/Security-Considerations
Next: Contributors, Previous: Robot Exclusion, Up: Appendices [Contents][Index]
9.2 Security Considerations
When using Wget, you must be aware that it sends unencrypted passwords through the network, which may present a security problem. Here are the main issues, and some solutions.
- The passwords on the command line are visible using
ps. The best way around it is to usewget -i -and feed the URLs to Wget’s standard input, each on a separate line, terminated by C-d. Another workaround is to use.netrcto store passwords; however, storing unencrypted passwords is also considered a security risk. - Using the insecure basic authentication scheme, unencrypted passwords are transmitted through the network routers and gateways.
- The FTP passwords are also in no way encrypted. There is no good solution for this at the moment.
- Although the “normal” output of Wget tries to hide the passwords, debugging logs show them, in all forms. This problem is avoided by being careful when you send debug logs (yes, even when you send them to me).
