\n<\/p>\n
In today’s world, securing your Linux servers from unauthorized access is more crucial than ever. One effective way to enhance your server’s security is by implementing an idle timeout for SSH (Secure Shell) sessions. This article will guide you through the steps to configure secure SSH idle timeout settings on your Linux servers.<\/p>\n
<\/p>\n
<\/p>\n
SSH is a powerful tool for managing remote servers, but it can also pose security risks if sessions are left open and unattended. An idle SSH session can be exploited by malicious users if they gain access to the terminal. By setting an idle timeout, you can automatically disconnect sessions after a specified period of inactivity, reducing the risk of unauthorized access.<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Begin by accessing your Linux server via SSH. Use your preferred terminal program and execute the following command:<\/p>\n
<\/p>\n
bash
\nssh username@server_ip<\/p>\n
<\/p>\n
Replace <\/p>\n <\/p>\n Once logged in, you need to edit the SSH configuration file, typically located at <\/p>\n bash <\/p>\n <\/p>\n Look for the following parameters in the <\/p>\n ClientAliveInterval<\/strong>: This value defines the time (in seconds) the server will wait before sending a message to the client requesting a response. Setting this to 300 means the server will wait 5 minutes.<\/p>\n \n<\/li>\n <\/p>\n ClientAliveCountMax<\/strong>: This value dictates how many times the server will send a “keep-alive” message without a response before it disconnects the client. Setting this to 0 means that it will disconnect after one missed response.<\/p>\n \n<\/li>\n \n<\/ul>\n <\/p>\n Add the following lines to the file (or modify them if they already exist):<\/p>\n <\/p>\n bash <\/p>\n <\/p>\n If you want to enforce a timeout from the client side as well, add the following lines to your user’s SSH configuration file, which is located at <\/p>\n bash <\/p>\n Add the following lines:<\/p>\n <\/p>\n bash <\/p>\n <\/p>\n After you make the changes, be sure to save the file and exit the text editor. For <\/p>\n <\/p>\n For the changes to take effect, you will need to restart the SSH service. Use the following command:<\/p>\n <\/p>\n bash <\/p>\n <\/p>\n You can now verify that your SSH idle timeout is working as expected. Leave an SSH session open and do not interact with it for the duration set in <\/p>\n <\/p>\n In addition to configuring an idle timeout, consider implementing other security measures such as:<\/p>\n <\/p>\n <\/p>\n <\/p>\n \n<\/ul>\n <\/p>\n <\/p>\n Implementing an SSH idle timeout is a simple yet effective way to bolster the security of your Linux servers. By following the steps outlined in this article, you can protect your server from potential unauthorized access through unattended sessions. Remember that security is an ongoing process, and regularly reviewing your configurations is essential to maintaining a secure environment.<\/p>\n <\/p>\n For more tips and guides on enhancing your server security, stay tuned to the WafaTech Blog!<\/p>\n\n","protected":false},"excerpt":{"rendered":" In today’s world, securing your Linux servers from unauthorized access is more crucial than ever. One effective way to enhance your server’s security is by implementing an idle timeout for SSH (Secure Shell) sessions. This article will guide you through the steps to configure secure SSH idle timeout settings on your Linux servers. Why Set […]<\/p>\n","protected":false},"author":2,"featured_media":2966,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[22],"tags":[391,1579,265,447,302,770,706],"class_list":["post-2965","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-security","tag-configuring","tag-idle","tag-linux","tag-secure","tag-servers","tag-ssh","tag-timeout","et-has-post-format-content","et_post_format-et-post-format-standard"],"yoast_head":"\nusername<\/code> with your actual username and server_ip<\/code> with the IP address of your server.<\/p>\n2. Modify the SSH Configuration File<\/h3>\n
\/etc\/ssh\/sshd_config<\/code>. Open the file using a text editor with elevated privileges. For example, use nano<\/code> or vi<\/code>:<\/p>\n
\nsudo nano \/etc\/ssh\/sshd_config<\/p>\n3. Add or Modify Timeout Settings<\/h3>\n
sshd_config<\/code> file. If they do not exist, you can add them:<\/p>\n<\/p>\n
\nClientAliveInterval 300
\nClientAliveCountMax 0<\/p>\n4. (Optional) Configure Timeout for the Client<\/h3>\n
~\/.ssh\/config<\/code>. If it doesn’t exist, you can create it:<\/p>\n
\nnano ~\/.ssh\/config<\/p>\n
\nServerAliveInterval 300
\nServerAliveCountMax 0<\/p>\n5. Save Your Changes<\/h3>\n
nano<\/code>, you can do this by pressing CTRL + X<\/code>, then Y<\/code> to confirm, and Enter<\/code> to save.<\/p>\n6. Restart the SSH Service<\/h3>\n
\nsudo systemctl restart sshd<\/p>\n7. Test Your Configuration<\/h3>\n
ClientAliveInterval<\/code>. After the timeout period, you should see that the SSH session disconnects.<\/p>\nAdditional Security Measures<\/h2>\n
<\/p>\n
Conclusion<\/h2>\n