Re: wget: Arbitrary file overwriting/appending/creating and other vulnerabilities
Quoting Jan Minar <[EMAIL PROTECTED]>: > (2) Use alternative retrieval programs, such as pavuk, axel, or > ncftpget. FWIW pavuk is much worse securitywise than wget. I've been working on patching pavuk for a few months, and it has lots of strcpy() and sprintf() calls that lead to buffer overflows, bad printf() statements that lead to format string bugs and so on. I think lots of people with security expertise would agree that buffer overflows and format string bugs are bigger problems than the types of vulnerabilities you have described in wget, even if the smaller stuff shouldn't be neglected either. -- Ulf Harnhammar http://www.advogato.org/person/metaur/ a member of the Debian Security Audit Project http://www.debian.org/security/audit/
Re: keep-session-cookies
* Deryck Thake <[EMAIL PROTECTED]> [041125 20:01]: > Is the keep-session-cookies feature working for any wget 1.9.* on > Windows? I can see that the session cookie is saved in the cookies.txt > file but it does not appear to be used when I rerun wget with the the > load-cookies option. You muste use the keep-session-cookies to load the cookies too. If you don't, cookies are discarded when loaded. /Nicolas.
Re: wget: Arbitrary file overwriting/appending/creating and other vulnerabilities
El 09/12/2004, a las 10:14, Jan Minar escribió: (0) Wget authors are/were incompetent. Everything else is a corollary. That's a very aggressive stance to take, and not likely to be productive. Patches, for example, would be more productive. -- Mauro Tortonesi in a private mail exchange with me And did you ask Mauro for his permission before disclosing the contents of his private correspondence with you? I am doubtful that he would appreciate your disclosure, given that you then used it to attack the project of which he is the maintainer.
Re: cookies protected site problem
On Thu, 9 Dec 2004, Jean Francois Ortolo wrote: Hi Sir <...> Best regards. Jean Francois Ortolo Hi Sir I present my apologies, the problem is solved now. In fact, there was only one session cookie, the only remaining problem being to properly choose the succession of urls to visit. I've only one question yet, not specifically related to wget: Is a browser obliged to send the session cookie it has, while retrieving frame urls ? Thank you very much for your help. Best regards. Jean Francois Ortolo
wget bug with large files
I got a crash in wget downloading a large iso file (2,4 GB) newdeal:/pub/isos# wget -c ftp://ftp.belnet.be/linux/fedora/linux/core/3/i386/iso/FC3-i386-DVD.iso --09:22:17-- ftp://ftp.belnet.be/linux/fedora/linux/core/3/i386/iso/FC3-i386-DVD.iso => `FC3-i386-DVD.iso' Resolving ftp.belnet.be... 193.190.198.20 Connecting to ftp.belnet.be[193.190.198.20]:21... connected. Accesso come utente anonymous ... Login eseguito! ==> SYST ... fatto. ==> PWD ... fatto. ==> TYPE I ... fatto. ==> CWD /linux/fedora/linux/core/3/i386/iso ... fatto. ==> SIZE FC3-i386-DVD.iso ... fatto. ==> PASV ... fatto. ==> REST 2079173504 ... fatto. ==> RETR FC3-i386-DVD.iso ... fatto. 100%[+=>] 2,147,470,560 60.39K/s ETA 00:00wget: progress.c:704: create_image: Assertion `insz <= dlsz' failed. Aborted then I tried to resume the download .. newdeal:/pub/isos# wget -c ftp://ftp.belnet.be/linux/fedora/linux/core/3/i386/iso/FC3-i386-DVD.iso --09:41:40-- ftp://ftp.belnet.be/linux/fedora/linux/core/3/i386/iso/FC3-i386-DVD.iso => `FC3-i386-DVD.iso' Resolving ftp.belnet.be... 193.190.198.20 Connecting to ftp.belnet.be[193.190.198.20]:21... connected. Accesso come utente anonymous ... Login eseguito! ==> SYST ... fatto. ==> PWD ... fatto. ==> TYPE I ... fatto. ==> CWD /linux/fedora/linux/core/3/i386/iso ... fatto. ==> SIZE FC3-i386-DVD.iso ... fatto. ==> PASV ... fatto. ==> REST -2147476576 ... REST fallito, ricomincio dall'inizio. (restarting from beginning) ==> RETR FC3-i386-DVD.iso ... fatto. [ <=>] 551,648 63.87K/s Here it deleted the old iso image (2,1GB downloaded) and started from the beginning .. shouldn't it save the new file with a .1 suffix ? Let me know if I can help you tracking this bug Thanks, -- Roberto Sebastiano <[EMAIL PROTECTED]>
