ubiquity

Merge lp://staging/~mdeslaur/ubiquity/fix-random-seed into lp://staging/ubiquity

  1. fix-random-seed
  2. Merge into trunk
Proposed by Marc Deslauriers
Status: Merged
Approved by: Mathieu Trudel-Lapierre
Approved revision: 6353
Merged at revision: 6382
Proposed branch: lp://staging/~mdeslaur/ubiquity/fix-random-seed
Merge into: lp://staging/ubiquity
Diff against target: 36 lines (+9/-2)
2 files modified
debian/changelog (+7/-0)
scripts/plugininstall.py (+2/-2)
To merge this branch: bzr merge lp://staging/~mdeslaur/ubiquity/fix-random-seed
Reviewer Review Type Date Requested Status
Mathieu Trudel-Lapierre Approve
Dimitri John Ledkov (community) Needs Information
Review via email: mp+280018@code.staging.launchpad.net

Description of the change

  scripts/plugininstall.py: Write initial random seed to systemd
  location (LP: #1523199)

To post a comment you must log in.
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

As of 4.2 kernel there is no need for random seed. Thus systemd seed service will do nothing, and we shouldn't need to fix this in xenial.

Maybe this needs to be fixed in prior releases, i do not know.

http://lists.freedesktop.org/archives/systemd-devel/2015-June/033297.html

http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.2-Crypto-Akcipher-PKE

http://marc.info/?l=linux-kernel&m=143496272614455&w=2

Thus why should we fix this?! I think we should like remove it completely.

review: Needs Information
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

The Jitter RNG linked above is for the Crypto API code, and isn't relevant for the random device.
The random device still needs to be seeded at boot.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches

to status/vote changes: