Bug#760029: systemd: doesn't initialise RANDOM_SEED upon installation

[Michael Biebl]

Hi

Am 04.02.2016 um 09:11 schrieb Michael Biebl:
> Am 04.02.2016 um 07:42 schrieb Raphael Geissert:
>> On Feb 4, 2016 3:11 AM, "Michael Biebl" <biebl at debian.org> wrote:
> 
>> Oh, it must have fallen through the cracks.
>> Anyway, the problem at hand is the lack of entropy during first boot. Think
>> about a raspberry pi for an example.
> 
> Ok, what exactly is the problem here. I mean, we shipped the current
> setup with jessie and I don't remember any entropy related bug reports.
> I installed systemd on my PI without problems.
> What exactly happens/can happen, if we don't (pre)initialize the random
> seed? Do you have any bug reports, which are still valid with modern
> Linux kernels?

So, I thought about this a bit more: Say we do the following in postinst

if [ -z "$2" ] ; then
   /lib/systemd/systemd-random-seed save
fi

This would create /var/lib/systemd/random-seed upon first installation.

What happens though, if someone uses debootstrap to create an image
which is the deployed on 100s of machines.
Those images would all ship an identical /var/lib/systemd/random-seed.
Isn't that a problem?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160204/8ee18003/attachment-0002.sig>