Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Access from anywhere: securing FOP2

Access from anywhere: securing FOP2

Scheduled Pinned Locked Moved Support
6 Posts 4 Posters 154 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    S
    sub0
    wrote on last edited by
    #1

    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?

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      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,

      1 Reply Last reply
      0
      • A
        A
        AlexRS
        wrote on last edited by
        #3

        Try to use fail2ban if FOP2 write bad auth in log.

        1 Reply Last reply
        0
        • S
          S
          sub0
          wrote on last edited by
          #4

          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.

          1 Reply Last reply
          0
          • N
            N
            nicolas
            wrote on last edited by
            #5

            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,

            1 Reply Last reply
            0
            • J
              J
              JSANCHEZ1008
              wrote on last edited by
              #6

              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.

              1 Reply Last reply
              0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              Powered by NodeBB Contributors
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups