Merge lp:~mdeslaur/ubiquity/fix-random-seed into lp:ubiquity
Proposed by
Marc Deslauriers
on 2015-12-09
| Status: | Merged |
|---|---|
| Approved by: | Mathieu Trudel-Lapierre on 2016-02-24 |
| Approved revision: | 6353 |
| Merged at revision: | 6382 |
| Proposed branch: | lp:~mdeslaur/ubiquity/fix-random-seed |
| Merge into: | lp: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:~mdeslaur/ubiquity/fix-random-seed |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mathieu Trudel-Lapierre | 2016-02-01 | Approve on 2016-02-01 | |
| Dimitri John Ledkov | 2015-12-09 | Needs Information on 2015-12-09 | |
|
Review via email:
|
|||
Description of the Change
scripts/
location (LP: #1523199)
To post a comment you must log in.
| 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.
review:
Approve


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.freedeskt op.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=1434962726144 55&w=2
Thus why should we fix this?! I think we should like remove it completely.