From: Bruno Thomsen <bth@kamstrup.com>
To: "chf.fritz@googlemail.com" <chf.fritz@googlemail.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCHv2 1/2] strongswan: version bump 5.2.2 -> 5.3.2
Date: Tue, 7 Jul 2015 13:07:46 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D01BD2C6053@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <1435994592.2885.4.camel@googlemail.com>
Hi Christoph,
> > STRONGSWAN_URL := http://download.strongswan.org/$(STRONGSWAN).$(STRONGSWAN_SUFFIX)
>
> Changing here to https to get this security related package would be nice.
Yes, I just tested https and it works flawlessly.
I will send it as a new patch so it's highlighted in ptxdist short log, that packages should preferably be downloaded from https/ftps urls.
> By the way, is there any work in the pipe to get PGP-Signature verification into ptxdist instead of "md5summing"?
Yes, PGP-signature verification could be nice. Would you bundle all public keys in ptxdist git repo?
An easy step stone could be to add SHA256 hash support in ptxdist.
Pseudo code:
if STRONGSWAN_SHA256 exist:
hash = sha256sum STRONGSWAN_SOURCE
return (hash == STRONGSWAN_SHA256)
else
hash = md5sum STRONGSWAN_SOURCE
return (hash == STRONGSWAN_MD5)
After looking at how the md5 hash check is performed, I think it's easier to add sha256 hashes to all rules and then change hash function.
/Bruno
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-07 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 9:46 Bruno Thomsen
2015-07-01 9:46 ` [ptxdist] [PATCHv2 2/2] strongswan: removed md5 hash and des encryption support Bruno Thomsen
2015-07-04 7:23 ` [ptxdist] [PATCHv2 1/2] strongswan: version bump 5.2.2 -> 5.3.2 Christoph Fritz
2015-07-07 13:07 ` Bruno Thomsen [this message]
2015-07-14 11:23 ` Michael Olbrich
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=915054555B5659448ACF8A70E114824D01BD2C6053@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.com \
--cc=chf.fritz@googlemail.com \
--cc=ptxdist@pengutronix.de \
/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