From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] downloading package from htts with certificate
Date: Wed, 04 Aug 2010 10:13:13 -0300 [thread overview]
Message-ID: <4C596769.8000603@zacarias.com.ar> (raw)
In-Reply-To: <AANLkTi==fwdy_k4a0bu3zVtcCk-m1kCOHMuSM=cbAftp@mail.gmail.com>
On 08/04/2010 08:41 AM, Belisko Marek wrote:
> Hi,
>
> I'm working on splashy package integration to buildroot but I'm facing
> a problem with package downloading.
> Package is stored on place where SSL certificate is necessary. My output is:
>
>>>> splashy 0.3.13 Downloading
> --2010-08-04 13:28:28--
> https://alioth.debian.org/frs/download.php/2691//splashy-0.3.13.tar.gz
> Resolving alioth.debian.org... 217.196.43.134
> Connecting to alioth.debian.org|217.196.43.134|:443... connected.
> ERROR: cannot verify alioth.debian.org's certificate, issued by
> `/O=Debian/CN=ca.debian.org/emailAddress=debian-admin at debian.org':
> Self-signed certificate encountered.
> To connect to alioth.debian.org insecurely, use `--no-check-certificate'.
> Unable to establish SSL connection.
> --2010-08-04 13:28:28--
> http://buildroot.net/downloads/sources//splashy-0.3.13.tar.gz
> Resolving buildroot.net... 140.211.167.224
> Connecting to buildroot.net|140.211.167.224|:80... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: http://sources.buildroot.net//splashy-0.3.13.tar.gz [following]
> --2010-08-04 13:28:29-- http://sources.buildroot.net//splashy-0.3.13.tar.gz
> Resolving sources.buildroot.net... 88.198.64.109
> Connecting to sources.buildroot.net|88.198.64.109|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2010-08-04 13:28:29 ERROR 404: Not Found.
>
> How can I override this to properly download source of package?
>
> Thanks in advance,
>
> Marek
Hi.
You can add the necessary option for wget in the configuration.
Build options -> Commands -> Wget command.
Add what's recommended "--no-check-certificate" to the options already
present there. That will make it ignore all self-signed certificates.
The problem is alioth.debian.org using a self-signed certificate instead
of a proper one.
Regards.
prev parent reply other threads:[~2010-08-04 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 11:41 [Buildroot] downloading package from htts with certificate Belisko Marek
2010-08-04 13:13 ` Gustavo Zacarias [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C596769.8000603@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox