Bug #765
Template: generate new ssh host keys
| Status: | New | Start date: | 11/27/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  William Leonard |
% Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Resolution: | Operating System: | CentOS 5 | ||
| Reproduceable: | Architecture: | 64Bit |
Description
New ssh host keys should be generated.
Please let me know your thoughts so I don't work too much in a certain direction and have to change that.
History
Updated by William Leonard 6 months ago
This one is easy in CentOS. Simply deleting etc/ssh/ssh_host_* from the template worked. I would recommend the template have it removed, but also checked during the rebuild. I could go either way. I'll see if this works on the other distros.
Updated by William Leonard 6 months ago
I'd be fine with requiring the template maker to do this, but there are several other things like this that HyperVM handles, for instance the inittab and fstab files.
Updated by William Leonard 3 months ago
Anyone want to chime in on this? I just don't like forcing changes on people. Should this be up to the template maker or should HyperVM do this on the template capture?
Updated by William Leonard 2 months ago
- Operating System set to CentOS 5
- Architecture set to 64Bit
Unlike CentOS, Debian (maybe Ubuntu) don't generate host keys when none exist. You have to run something to do this. So there will have to be a method added to do a 1 time startup process. This differs from what I did with Fedora 16. With Fedora 16 the startup script runs every time the guest is rebooted from the HyperVM control panel.
Updated by Philipp Esselbach 2 months ago
dpkg-reconfigure openssh-server
should do the trick. Same with Ubuntu after it based on Debian.