From yann at pleiades.fr.eu.org Sun Sep 9 14:14:28 2007 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Sun, 09 Sep 2007 14:14:28 +0200 Subject: [csw-announce] WARNING: upgrading ssh will kill ssh connections under Solaris 10 Message-ID: <1189340068.6098.2.camel@celaeno> A new openssh package will soon land in the unstable repository but due to a bug in SMF support, upgrading to this package will kill all previous sshd processes 60 seconds after the previous package is removed, thus closing all sshd connections. This problem only affects Solaris >= 10. You are then strongly advised to perform this upgrade with no user logged by ssh, and it is also recommended to use a console or a non-ssh remote access to perform the upgrade. If you run pkg-get from a ssh connection, the connection will be closed 60s after the previous pakages removal, this could lead in the new ssh package incorrectly installed, if it happens before the upgrade is finished Also, if the ssh service has problem being restarted correctly, you would not be able to reconnect to your computer remotely. If you have only a ssh access avaible, you could launch another ssh daemon on non-standard port: /opt/csw/sbin/sshd -p 2022 and then connect to your computer daemon using this port: ssh -p 2022 yourcomputer This connection will not be monitored by SMF and hence will not be closed by the upgrade process. This new package solves this issue and next upgrades will not suffer from this problem. Yann From yann at pleiades.fr.eu.org Sun Sep 9 14:14:28 2007 From: yann at pleiades.fr.eu.org (Yann Rouillard) Date: Sun, 09 Sep 2007 14:14:28 +0200 Subject: [csw-announce] WARNING: upgrading ssh will kill ssh connections under Solaris 10 Message-ID: <1189340068.6098.2.camel@celaeno> A new openssh package will soon land in the unstable repository but due to a bug in SMF support, upgrading to this package will kill all previous sshd processes 60 seconds after the previous package is removed, thus closing all sshd connections. This problem only affects Solaris >= 10. You are then strongly advised to perform this upgrade with no user logged by ssh, and it is also recommended to use a console or a non-ssh remote access to perform the upgrade. If you run pkg-get from a ssh connection, the connection will be closed 60s after the previous pakages removal, this could lead in the new ssh package incorrectly installed, if it happens before the upgrade is finished Also, if the ssh service has problem being restarted correctly, you would not be able to reconnect to your computer remotely. If you have only a ssh access avaible, you could launch another ssh daemon on non-standard port: /opt/csw/sbin/sshd -p 2022 and then connect to your computer daemon using this port: ssh -p 2022 yourcomputer This connection will not be monitored by SMF and hence will not be closed by the upgrade process. This new package solves this issue and next upgrades will not suffer from this problem. Yann