WGET SSL certificate error for sourceforge
Hi. Linux user here. I'm trying to use wget to download systemrescuecd and I get an SSL error for the sourceforge site.
$ wget https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/1.2.3/systemrescuecd-x86-1.2.3.iso
--2009-08-29 18:30:13-- https://sourceforge.net/projects/systemrescuecd/files/sysresccd-x86/1.2.3/systemrescuecd-x86-1.2.3.iso
Resolving sourceforge.net... 184.108.40.206
Connecting to sourceforge.net|220.127.116.11|:443... connected.
ERROR: cannot verify sourceforge.net's certificate, issued by `/C=US/O=Equifax/OU=Equifax Secure Certificate Authority':
Unable to locally verify the issuer's authority.
To connect to sourceforge.net insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
I can download fine if I click on the Direct Download URL, which is https://sourceforge.net/projects/system ... o/download
. But that is firefox doing the download, not wget. Interestingly, firefox downloads from http://softlayer.dl.soruceforge.net
. But on the Sourceforge project page for SystemRescueCD, the actual file location seems to be http://sourceforge.net/projects/systemr ... o/download
. Note that this is the same file I'm trying to get with wget, except that it is http protocol instead of https.
So I can wget the file using http, but I fail using https. Does it make any difference in terms of security?
I also have a suggestion. On this page: http://www.sysresccd.org/Download
there is a warning suggesting that the file should be downloaded using wget. This implies that it is not recommended
to use the provided direct download link (which doesn't work with wget due to the SSL certificate problem). The reason for making this a "warning" rather than just a hint or tip is not clear. The fact that it is couched as a warning suggests there is something dangerous about other download methods. Since the location of the file that can be downloaded by wget is not provided anywhere on the http://www.sysresccd.org/Download
page, it is actually not easy to get it using wget. I recommend clarification to explain why the suggestion to use wget is expressed as a warning, and that you add the location of the file to the page so that wget users can actually get it.