Host * StrictHostKe圜hecking no UserKnownHostsFile=/dev/null User ec2-user To over this you need to add the following configurations in your ssh settings Lastly is the Settings in the putty, so once you open the putty select the default settings-> Connection-> Seconds between Keppalives (120)-> click Apply->Click SaveĪlso Every time you connect to the New server it asks for the key checking and if you are working in an autoscale environment and have created the automated scripts using the ssh than those would not run unless you access the fingerprint and add the servers under your knownhosts in the Linux. Than you need to restart the ssh service to make this effective.
Vim /etc/ssh/sshd_config # ssh ideal timeout value ClientAliveInterval 120
If you are using the Bastion host in your corporate environment to connect to the Different Server than you can edit the sshd_config file and make an entry as below to increase the session timeout for the ssh ssh/config Host * ServerAliveInterval 120 chmod 600. Setup the ServerAliveInterval in your user account to provide the extended time for session timeout i.e. Although you can prevent the session timeout from the server and client. While working on the Linux server its common to face the ssh session timeout from the server due to ideal session.
0 kommentar(er)
