[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 18 May 2010 09:50:27 +0200
From: Ludwig Nussel <ludwig.nussel@...e.de>
To: oss-security@...ts.openwall.com
Subject: Re: [oCERT-2010-001] multiple http client unexpected download filename vulnerability
Florian Weimer wrote:
> * Daniele Bianco:
>
> > Additionally, unsafe behaviours have been found in wget and lwp-download in
> > the case of HTTP 3xx redirections during file downloading. The two
> > applications automatically use the URL's filename portion specified in the
> > Location header.
>
> Thanks. In another venue, I wrote:
>
> > The difficult thing is that most likely, there are setups out there
> > which expect this particular behavior. If we change the default
> > behavior, we need an option in wgetrc to turn back on the old one. 8-(
wget doesn't overwrite existing files by default anyways. Instead it appends a
suffix .1, .2 etc to the newly downloaded file. wget also prints the file name
it used. So IMO it's perfectly fine and useful for wget to take the server
provided file name by default.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
