![](https://seccdn.libravatar.org/avatar/a257fa0591438f3c6ad1c8bc48ce0fdc.jpg?s=120&d=mm&r=g)
On Fri, 29 Nov 2013 15:12:20 +0100 cagsm cagsm wrote:
... Having a rather old opensuse machine that got constantly upgraded over many years ...
This background information is too ambiguous. Has the hardware been upgraded and not the OS? What OS version is presently installed on the old machine? Was it installed 'fresh' or has there been an upgrade path?
am ... installing a newer 12.3 version ... The machine is being used by multiple remote ssh clients and other things ... ... Also the key files inside seem to have thei original hostname included when the sshd generated these private keys
When you actually swap the machines out, you can assign the new machine the same hostname as the original, can't you? I'm not saying this is necessary, but if it can be done, why not do it? YMMV, but my approach would be to create .tar.gz archives of the old and new /etc/ssh directories for safekeeping & experimentation. Then, on the new machine, I'd rename the /etc/ssh directory /etc/.ssh and decompress the old one in it's place. I'd then copy over any files or directories existing in the new (now 'hidden') directory that do _not_ appear in the old. Finally, I'd 'diff' (compare) and reconcile settings in the 'old' sshd configuration file (now at /etc/ssh/sshd_config) with the 'new' one (now at /etc/.ssh/sshd_config) and substitute the result into production to test. Obviously, you know to restart sshd each time you modify the configuration (#> 'systemctl restart sshd'). hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org