<![CDATA[Access from anywhere: securing FOP2]]>We have a customer that needs access to FOP2 from any public IP. They have been using Fonality's HUD and would like a similar experience..

Apart from strong passwords, what are the best practices for securing FOP2?

]]>http://localhost:4567/topic/2443/access-from-anywhere-securing-fop2RSS for NodeTue, 27 Oct 2026 05:47:59 GMTTue, 03 Jan 2017 02:51:38 GMT60<![CDATA[Reply to Access from anywhere: securing FOP2 on Tue, 15 Sep 2020 12:51:24 GMT]]>Hi Nicolas. FOP2 writes bad authentication attempts logs only for regular user https://mypbx.com/fop2 but not for admin user https://mypbx.com/fop2/admin

Thanks in advance.

]]>http://localhost:4567/post/10723http://localhost:4567/post/10723Tue, 15 Sep 2020 12:51:24 GMT<![CDATA[Reply to Access from anywhere: securing FOP2 on Mon, 13 Feb 2017 21:06:38 GMT]]>FOP2 does write an audit log if you enable it via the -a command line parameter, including Bad authentication attempts. Try adding -a /var/log/fop2_audit.log to the startup parameters in the /etc/sysconfig/fop2 file if you want.

As for passwords on the wire, they are hashed/encrypted, they are not transferred plain text.

Best regards,

]]>http://localhost:4567/post/10722http://localhost:4567/post/10722Mon, 13 Feb 2017 21:06:38 GMT<![CDATA[Reply to Access from anywhere: securing FOP2 on Mon, 13 Feb 2017 19:03:32 GMT]]>AFAIK FOP2 does not write bad auth anywhere. Does it?

Also AFAIK, fop2 auth occurs over port 4445 so https would not encrypt those passwords.

Thanks for great support as always.

]]>http://localhost:4567/post/10721http://localhost:4567/post/10721Mon, 13 Feb 2017 19:03:32 GMT<![CDATA[Reply to Access from anywhere: securing FOP2 on Wed, 04 Jan 2017 06:44:20 GMT]]>Try to use fail2ban if FOP2 write bad auth in log.

]]>http://localhost:4567/post/10720http://localhost:4567/post/10720Wed, 04 Jan 2017 06:44:20 GMT<![CDATA[Reply to Access from anywhere: securing FOP2 on Tue, 03 Jan 2017 22:05:10 GMT]]>you can use https and strong passwords. You can limit access to /fop2/admin via .htaccess or similar as you might probably do not want access to the manager from everywhere.

Best regards,

]]>http://localhost:4567/post/10719http://localhost:4567/post/10719Tue, 03 Jan 2017 22:05:10 GMT