On 3/3/24 10:35 AM, Tim Rühsen wrote:
Wget tries not to overwrite files.
But if you want to remove the old file, no matter what, why don't you
remove (or rename) that file before calling wget?
Thanks for the response. I understand that I can do that, but the wget
is part of an automated
Thanks vulnerabilityspotter,
are there any insights why this specific integer overflow is a
vulnerability? ("potential" is not enough)
TL;DR for the audience:
An AI generated vulnerability report. I mostly agree with what has been
written for curl at https://github.com/curl/curl/issues/12983
On 2/25/24 03:40, Mark Sapiro wrote:
As far as I can tell, the only way to get wget to overwrite an existing
file is with the `-O` option, but I want to use `--content-disposition`
to write the output to the filename in the Content-Disposition: header.
This works, but if the filename already