RFE: seed /dev/urandom with random data from metadata service when available
Bug #1198297 reported by
Matthew Miller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
If a cloud provider offers random data to instances via a metadata service, like, oh, say, https:/
Related branches
lp:~harlowja/cloud-init/cloud-init-seedy
- cloud-init Commiters: Pending requested
-
Diff: 341 lines (+263/-14)5 files modifiedcloudinit/config/cc_seed_random.py (+61/-0)
cloudinit/exceptions.py (+21/-0)
cloudinit/sources/DataSourceConfigDrive.py (+30/-14)
config/cloud.cfg (+1/-0)
tests/unittests/test_handler/test_handler_seed_random.py (+150/-0)
| Changed in cloud-init: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in cloud-init: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Scott Moser (smoser) wrote | #1 |
| Changed in cloud-init: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Matthew Miller (mattdm) wrote | #2 |
Revision history for this message
| James Falcon (falcojr) wrote | #3 |
To post a comment you must log in.
This is fixed in cloud-init 0.7.7