Remove authorized keys when custom image is created
Registered by
John Haan
When guest OS is spawned the public key is injected into the authorized_keys of vm.
After converting the vm to custom image, the contents of athorized_key file is still remain in the custom image.
Even though, user has other keypair when a new vm is spawned from the custom image,
other user can access the new vm who has keypair of previous vm.
Therefore the authorized key file need to be reset whenever custom image is created.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- John Haan
- Direction:
- Needs approval
- Assignee:
- John Haan
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- John Haan
- Completed by
- Russell Bryant
Related branches
Related bugs
Sprints
Whiteboard
I think this is outside of the scope of what Nova should be doing. We minimize Nova's interaction with whatever is inside the VM. --russellb
(?)
