I am not sure if this is the right sub, but yesterday I was having some issues with login with my user and was getting 403 error if I am not wrong and noticed that the NGINX version is exposed, which is a bad practice.

So if someone from the admins of Lemmy.world see this message, maybe they can change the NGINX config and hide the version flag by setting “server_tokens off;”.

      • half@lemmy.world
        link
        fedilink
        arrow-up
        20
        ·
        1 year ago

        My pet theory is that NGINX was designed by a pen-tester who realized that all they needed to do to make the majority of SMBs expose their web servers to the internet was outperform Apache

  • s38b35M5@lemmy.world
    link
    fedilink
    arrow-up
    36
    arrow-down
    1
    ·
    edit-2
    1 year ago

    They likely won’t see this unless you tag them or cross post to !support@lemmy.world

    That said, I suspect the version is what’s standard in the docker image, so hidden or not, it’s easy to discover.

    Edit: on the other hand, does the latest nginx get pulled at time of creation?

    • tool@r.rosettast0ned.com
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      Edit: on the other hand, does the latest nginx get pulled at time of creation?

      It depends on how you have your docker compose file set up. If you pin the version, no, it’s never going to get updated unless a new version with that exact tag is released. If you omit the tag, it’s going to default to whatever is tagged as latest in the image repository, and that’s only going to actually update the image when you either manually pull the image or relaunch the compose stack.

      If you want it to auto-update without relaunching the stack or manually pulling the latest image, you’d have to set up something like Watchtower and have it monitor that container.

  • squiblet@kbin.social
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    1 year ago

    Might as well hide the version, but if someone is going to try an exploit, they’ll just try it and see whether it works.

      • Midas@ymmel.nl
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        Obscuring version numbers is best practice. Trying exploits isn’t always trivial and by knowing the exact version number of the software it can be made a whole lot easier. Good post by OP though I do think it should’ve been a DM to Ruud.