To be safe, you enter the command to upgrade openssl on the existing ssh connection, and then restart the service. Don't disconnect from SSH. Then open a new SSH session and confirm that everything is normal before disconnecting the old SSH connection.
Log in to the VPS with SSH and upgrade directly with apt-get update and apt-get upgrade.
After the upgrade, although OpenSSL is still 1.0.1e, the BUG has been fixed.
Theoretically there will be no problems. In order to prevent problems, it is recommended to open a new SSH and try to log in successfully before disconnecting the existing SSH
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
To be safe, you enter the command to upgrade openssl on the existing ssh connection, and then restart the service. Don't disconnect from SSH. Then open a new SSH session and confirm that everything is normal before disconnecting the old SSH connection.
Choose a quiet time at night to upgrade. First simulate it several times in the experimental environment.
Ssh is theoretically influential
But this is only for statically compiled ssh
Generally, ssh is compiled dynamically
Just upgrade openssl
Linux upgrade openssl and php_openssl modules
Upgraded this morning.
Log in to the VPS with SSH and upgrade directly with apt-get update and apt-get upgrade.
After the upgrade, although OpenSSL is still 1.0.1e, the BUG has been fixed.
Theoretically there will be no problems. In order to prevent problems, it is recommended to open a new SSH and try to log in successfully before disconnecting the existing SSH