Hello,
here's my segfault. It requires some preparation.
Fetch
http://www.gnu.org/software/automake/manual/html_mono/automake.html
recursively as to have in current directory:
bash-2.05b$ tree www.gnu.org/
www.gnu.org/
`-- software
`-- automake
`-- manual
`-- html_mono
on machine 2 with wget version: Wget 1.9.1
i get error: not implemented !!
on machine 1 with wget Version: Wget 1.9+cvs-dev
everything is ok
here the command line:
wget -S -d -v --sslcafile=/env/config/cacert.pem
--directory-prefix=/env/update --http-user= --http-passwd=xx
--proxy=on
Claudio Fontana [EMAIL PROTECTED] writes:
here's my segfault. It requires some preparation.
[...]
Thanks for the detailed report and the stack trace. This patch should
fix the segmentation fault.
2005-05-10 Hrvoje Niksic [EMAIL PROTECTED]
* res.c (res_register_specs): Correctly
Hrvoje Niksic [EMAIL PROTECTED] writes:
Specifically I am interested in the correctness of the code that
loads the client certificates and checks for server certificates.
Here is the thing we definitely miss: Wget doesn't contain code that
checks the host identity presented by the server's
On Tue, 10 May 2005, Hrvoje Niksic wrote:
curl contains much more elaborate code in ssluse.c:verifyhost(). Although
I'm not sure Wget requires an exact replica of curl's logic, *some* check
seems necessary for, especially since we claim to verify the server's
certificate by default.
It does
Daniel Stenberg [EMAIL PROTECTED] writes:
It does require a replica, exact or not.
It's interesting that none of the OpenSSL examples include such code.
In fact, curl may be the single free application that attempts to get
this right!
If you verify a server certificate, you must make sure the
Werner Schmitt [EMAIL PROTECTED] writes:
on machine 2 with wget version: Wget 1.9.1
i get error: not implemented !!
on machine 1 with wget Version: Wget 1.9+cvs-dev
everything is ok
That is because the other machine has a newer (CVS) version of Wget
that correctly implements HTTPS
