Wednesday, May 24, 2017

How to protect saslauthd from local brute force attack?

There are numerous instructions over the internet to use saslauthd. I've tried to run the service. It gave me a surprise when I discovered that /run/saslauthd/mux socket and /usr/sbin/testsaslauthd are both available for non-privileged users. So when you have saslauthd started, it makes your system vulnerable.



What is the supposed way to restrict brute force? I've tried to google it, but google shows only SMTP and IMAP stuff, not saslauthd vulnerability itself.

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...