I checked on a different system; the same thing happens. Pre-upgrade -rw------- root/root 527 2004-07-01 00:56:34 ssh_host_key -rw-r--r-- root/root 331 2004-07-01 00:56:34 ssh_host_key.pub -rw------- root/root 887 2004-07-01 00:56:34 ssh_host_rsa_key -rw-r--r-- root/root 222 2004-07-01 00:56:34 ssh_host_rsa_key.pub -rw------- root/root 672 2004-07-01 00:56:36 ssh_host_dsa_key -rw-r--r-- root/root 602 2004-07-01 00:56:36 ssh_host_dsa_key.pub
Post-upgrade -rw------- 1 root root 527 Jun 12 23:25 ssh_host_key -rw-r--r-- 1 root root 331 Jul 1 2004 ssh_host_key.pub -rw------- 1 root root 887 Jul 1 2004 ssh_host_rsa_key -rw-r--r-- 1 root root 222 Jul 1 2004 ssh_host_rsa_key.pub -rw------- 1 root root 672 Jul 1 2004 ssh_host_dsa_key -rw-r--r-- 1 root root 602 Jul 1 2004 ssh_host_dsa_key.pub The woody ssh version was 1:3.4p1-1.woody.3 The sarge ssh version is 1:3.8.1p1-8.sarge.4 I'll let the maintainers set the priority, but this seems a fairly nasty behaviour because it can lead to a lot of unecessary warning messages about host identity changes. This is undesirable because it lowers peoples' level of watchfulness against compromised systems. Cheers Vince -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
