From: Johan Sagaert <sagaert.johan@proximus.be>
To: buildroot@busybox.net
Subject: [Buildroot] polarssl https download cercificate error.
Date: Tue, 31 Mar 2015 15:38:24 +0200 [thread overview]
Message-ID: <551AA350.1060203@proximus.be> (raw)
In-Reply-To: <551A7D32.7000404@zacarias.com.ar>
Gustavo Zacarias schreef op 31/03/2015 om 12:55:
> On 03/31/2015 06:25 AM, Johan Sagaert wrote:
>
>> Hi
>>
>> The link https://tls.mbed.org/download/polarssl-1.2.13-gpl.tgz seems to
>> be OK when
>> opening this from a browser.
>> Why is the download complaining ?
> Hi.
> That's because they were bought by ARM and got renamed to mbed tls.
> I'll send a patch to update the URL.
> Regards.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
Dear
That patch is not solving the problem :
It still reverts to downloading from buildroot.
As said before : https://tls.mbed.org/code/releases/polarssl-1.2.13-gpl.tgz
is working in the browser but buildroot fails to download the file.
Regards , Johan
>> polarssl 1.2.13 Downloading
--2015-03-31 15:29:05--
https://tls.mbed.org/code/releases/polarssl-1.2.13-gpl.tgz
Resolving tls.mbed.org... 79.170.91.36
Connecting to tls.mbed.org|79.170.91.36|:443... connected.
ERROR: certificate common name ?polarssl.org? doesn?t match requested
host name ?tls.mbed.org?.
To connect to tls.mbed.org insecurely, use ?--no-check-certificate?.
--2015-03-31 15:29:06-- http://sources.buildroot.net/polarssl-1.2.13-gpl.tgz
Resolving sources.buildroot.net... 176.9.16.109
Connecting to sources.buildroot.net|176.9.16.109|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1023128 (999K) [application/x-gzip]
next prev parent reply other threads:[~2015-03-31 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 9:25 [Buildroot] polarssl https download cercificate error Johan Sagaert
2015-03-31 10:55 ` Gustavo Zacarias
2015-03-31 13:38 ` Johan Sagaert [this message]
2015-03-31 13:51 ` Gustavo Zacarias
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=551AA350.1060203@proximus.be \
--to=sagaert.johan@proximus.be \
--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