RFC since this would be a bigger change in how we approach intra-cluster SSH access.
there are still a few parts that currently don't use SSHInfo, but would need to be switched over if we want to pursue this approach: - get_vnc_connection_info in PVE::API2::Nodes - 'upload' API endpoint in PVE::API2::Storage::Status - SSH proxy in pvesh these changes would need to happen coordinated with the patches from this RFC series! next steps afterwards: - unmerge known hosts in `pvecm updatecerts`, instead of merging -- to disentangle regular ssh from intra-cluster SSH -- to allow `ssh-keygen -f .. -R ..` to work properly again -- existing keys would still be preserved for not-yet-upgraded nodes, so this should be do-able without waiting for a major release.. - evaluate whether we want to split out -- the client config (we currently force a cipher order there) -- the client key (could live in /etc/pve/priv instead?) -- or even the sshd instance altogether (would allow not touching the regular sshd config at all) Fabian Grünbichler (2): fix #4886: write node SSH hostkey to pmxcfs fix #4886: SSH: pin node's host key if available src/PVE/Cluster/Setup.pm | 15 +++++++++++++++ src/PVE/SSHInfo.pm | 15 ++++++++++++++- 2 files changed, 29 insertions(+), 1 deletion(-) -- 2.39.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
