From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ibrdtn: add packaging rules for IBR-DTN and dtndht
Date: Thu, 1 Sep 2016 17:09:56 +0200 [thread overview]
Message-ID: <12c4c0cb-c5aa-8f61-adc2-5b502a50f52f@lespocky.de> (raw)
In-Reply-To: <6b808b5c-e3f6-6d63-9378-6495a15f3c1b@rohieb.name>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
Hei hei,
On 28.08.2016 20:36, Roland Hieber wrote:
> The key material would rather need to be
> generated at build time and/or put into projectroot/etc/ibrdtn/bpsec by
> the user.
Generating one key at build time for all your devices may be seen as a
security flaw, doesn't it? If you build update tarballs from your BSP
for example, which contain in some way private keys, an attacker could
replace those keys?
On the other hand, embedded devices often lack good random number
creation capabilities, so creating keys on the target may be bad, too?
Greets
Alex
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-09-01 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:53 Roland Hieber
2016-08-18 6:53 ` Michael Olbrich
2016-08-23 4:41 ` Roland Hieber
2016-08-25 11:02 ` Michael Olbrich
2016-08-25 15:11 ` Robert Schwebel
2016-08-28 5:27 ` Roland Hieber
2016-08-28 7:36 ` Robert Schwebel
2016-08-28 18:36 ` Roland Hieber
2016-09-01 9:58 ` Michael Olbrich
2016-09-01 15:09 ` Alexander Dahl [this message]
2016-08-29 7:42 ` Juergen Borleis
2016-08-18 10:15 ` Michael Olbrich
2016-08-28 5:32 ` [ptxdist] [PATCH v2] " Roland Hieber
2016-09-07 13:48 ` Michael Olbrich
2016-09-08 1:07 ` Roland Hieber
2016-09-08 6:35 ` 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=12c4c0cb-c5aa-8f61-adc2-5b502a50f52f@lespocky.de \
--to=post@lespocky.de \
--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