From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-10-09
Date: Wed, 10 Oct 2012 12:46:44 +0200 [thread overview]
Message-ID: <20121010124644.55d52fff@skate> (raw)
In-Reply-To: <874nm2aa44.fsf@macbook.be.48ers.dk>
On Wed, 10 Oct 2012 12:34:51 +0200, Peter Korsgaard wrote:
> Most of them, but not all:
>
> git grep https:// package/**/*.mk
> package/axel/axel.mk:AXEL_SITE = https://alioth.debian.org/frs/download.php/3015
> package/freerdp/freerdp.mk:FREERDP_SITE = https://github.com/downloads/FreeRDP/F
> package/inadyn/inadyn.mk:INADYN_SITE = https://github.com/downloads/troglobit/in
> package/libevent/libevent.mk:LIBEVENT_SITE = https://github.com/downloads/libeve
> package/libnspr/libnspr.mk:LIBNSPR_SITE = https://ftp.mozilla.org/pub/mozilla.or
> package/libnss/libnss.mk:LIBNSS_SITE = https://ftp.mozilla.org/pub/mozilla.org/s
> package/logrotate/logrotate.mk:LOGROTATE_SITE = https://fedorahosted.org/release
> package/multimedia/pulseaudio/pulseaudio.mk:# https://bugs.freedesktop.org/show_
> package/pcsc-lite/pcsc-lite.mk:PCSC_LITE_SITE = https://alioth.debian.org/frs/do
> package/python-nfc/python-nfc.mk:PYTHON_NFC_SITE = https://launchpad.net/nfcpy
> package/python-pygame/python-pygame.mk:PYTHON_PYGAME_SITE = https://bitbucket.or
> package/sconeserver/sconeserver.mk: https://sconeserver.svn.sourceforge.net/
> package/vim/vim.mk:VIM_SITE = https://vim.googlecode.com/hg
> package/vsftpd/vsftpd.mk:VSFTPD_SITE = https://security.appspot.com/downloads
>
> But yeah, I'll change the alioth downloads to http.
Ok. I am not a security expert, but I am not sure that downloading
those things from https:// gives any win over a http:// download. What
would be more interesting is to be able to verify the cryptographic
signature of those tarballs (or the signature of a hash of those
tarballs), to actually be able to verify that those tarballs have
really been emitted by whoever is supposed to emit those tarballs. But
that's another story, and there are probably many projects that don't
provide cryptographic signatures to verify the authenticity of
the tarballs.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-10 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 6:34 [Buildroot] [autobuild.buildroot.net] Build results for 2012-10-09 Thomas Petazzoni
2012-10-10 10:07 ` Peter Korsgaard
2012-10-10 10:29 ` Thomas Petazzoni
2012-10-10 10:34 ` Peter Korsgaard
2012-10-10 10:46 ` Thomas Petazzoni [this message]
2012-10-10 10:52 ` Gustavo Zacarias
2012-10-10 16:56 ` Alexandre Belloni
2012-10-10 17:32 ` Michael S. Zick
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=20121010124644.55d52fff@skate \
--to=thomas.petazzoni@free-electrons.com \
--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