From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10366] dropbear download url has changed
Date: Thu, 05 Oct 2017 20:31:31 +0000 [thread overview]
Message-ID: <bug-10366-163-0TmxdXXTcM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10366-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10366
Peter Korsgaard <jacmet@uclibc.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from Peter Korsgaard <jacmet@uclibc.org> ---
In what way has it changed?
http still works here:
wget http://matt.ucc.asn.au/dropbear/releases/dropbear-2017.75.tar.bz2
--2017-10-05 22:26:51--
http://matt.ucc.asn.au/dropbear/releases/dropbear-2017.75.tar.bz2
Resolving matt.ucc.asn.au (matt.ucc.asn.au)... 130.95.13.18,
2405:3c00:5200:100::18
Connecting to matt.ucc.asn.au (matt.ucc.asn.au)|130.95.13.18|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1623392 (1.5M) [application/x-bzip2]
Saving to: ?dropbear-2017.75.tar.bz2?
(and so does https):
wget https://matt.ucc.asn.au/dropbear/releases/dropbear-2017.75.tar.bz2
--2017-10-05 22:27:26--
https://matt.ucc.asn.au/dropbear/releases/dropbear-2017.75.tar.bz2
Resolving matt.ucc.asn.au (matt.ucc.asn.au)... 130.95.13.18,
2405:3c00:5200:100::18
Connecting to matt.ucc.asn.au (matt.ucc.asn.au)|130.95.13.18|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1623392 (1.5M) [application/x-bzip2]
Saving to: ?dropbear-2017.75.tar.bz2.1?
The server does send a HSTS header to ask browsers to use https, but that isn't
really a problem with wget.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-10-05 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 16:30 [Buildroot] [Bug 10366] New: dropbear download url has changed bugzilla at busybox.net
2017-10-05 16:34 ` [Buildroot] [Bug 10366] " bugzilla at busybox.net
2017-10-05 20:31 ` bugzilla at busybox.net [this message]
2017-10-05 21:09 ` bugzilla at busybox.net
2017-10-05 21:20 ` bugzilla at busybox.net
2017-10-06 12:37 ` bugzilla at busybox.net
2017-10-06 12:45 ` bugzilla at busybox.net
2017-10-06 12:57 ` bugzilla at busybox.net
2017-10-06 13:57 ` bugzilla at busybox.net
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=bug-10366-163-0TmxdXXTcM@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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