Do you throttle postfix, so you don't send gazillions of emails per second? For sure OVH panicked, they are fighting spammers off their servers.Not always... In my case for example, OVH were just complete idiots claiming forum mailers as SPAM.
Easiest way to secure your open-to-public ssh server: change the port and install 2-way authentication.
Problem solved. But the initial questions were not answered yet, what UDP ports are you getting packed on?
Code:# ss -naturl | grep udp
One week after re-enabling my server, I obviously had another attack.
The port was number 80.
Does this not present a hassle if you are using SCP to send multiple files at different time (but in a short period) from your desktop to the server. Would you not have to get a notification for input of the key each time?Easiest way to secure your open-to-public ssh server: change the port and install 2-way authentication.
Code:# ss -naturl | grep udp
Do you throttle postfix, so you don't send gazillions of emails per second? For sure OVH panicked, they are fighting spammers off their servers.
Is that that sucky Server Complete?Oh well worked out for the best anyway, the new data center we now use Go Racks is much better, even our customers notice the difference in both speed and cleaner packets
Of course it can, is the most important feature allowing you to manage the server load.Yeap postfix can not be throttled.
No, works great with ssh keys also.Does this not present a hassle if you are using SCP to send multiple files at different time (but in a short period) from your desktop to the server. Would you not have to get a notification for input of the key each time?
Of course it can, is the most important feature allowing you to manage the server load.
http://www.postfix.org/postconf.5.html
Start with default_destination_rate_delay, there are many other options to fine tune your delivery frequency.
No, works great with ssh keys also.
http://www.axivo.com/go/googleauth
Thanks, UDP 80? OP reply: The technique is very simple, the hacker sends a bunch of packets forcing the victim server to reply, generating implicitly a huge usage of bandwidth. There are hundreds of scripts like that on the Internet, taking advantage of unsecured servers. Changing the host won't do much, the attacker only needs to change the ip address. The only solution is to secure your server with the usual tools, Cloudflare, Nginx, Selinux, iptables, etc.Think he indicated port 80.
Of course it can, is the most important feature allowing you to manage the server load.
http://www.postfix.org/postconf.5.html
Start with default_destination_rate_delay, there are many other options to fine tune your delivery frequency.
No, works great with ssh keys also.
http://www.axivo.com/go/googleauth
You can scp without ssh keys. It will prompt you to enter the verification code and password.The Google authenticator is available in a .deb package, but you have to choose apples or oranges (keys or not).
We use essential cookies to make this site work, and optional cookies to enhance your experience.