What You Get After Running an SSH Honeypot for 30 Days (blog.sofiane.cc)

Article summary

The article discusses the results of running an SSH honeypot for 30 days, but the details of the article are not available. However, the comments reveal that exposing ports to the internet can be dangerous and attract malicious traffic. Commenters share their experiences with running servers and the importance of security measures. They also discuss the challenges of self-hosting email and the need for proper configuration to avoid delivery issues.

Main themes

• SSH security
• Server exposure
• Self-hosting email
• Security measures
• Malicious traffic
• Configuration challenges

What commenters say

• Exposing ports to the internet can attract thousands of malicious attempts to hack into a server, making it essential to use security measures like proxies or VPNs.
• Self-hosting email can be challenging due to delivery issues with certain providers, but proper configuration of DMARC, DKIM, and SPF can help.
• Disabling password authentication and using SSH keys is a more secure approach to accessing servers, as password authentication can be risky, especially on shared servers.
• Some argue that self-hosting email is not that hard, but getting emails delivered can be unpredictable and relies on other servers playing along.
• Using a static IP with a clean history can help with email delivery, but occasional glitches can still occur.
• Others believe that self-hosting email is possible and can be done successfully with the right configuration and security measures.
• The use of password authentication is considered obsolete and dangerous, and switching to SSH keys is recommended to improve security.
• Enabling both password and key authentication can be an alternative for those who prefer passwords, but it may not be the most secure approach.