Hi, I’m setting up a public wiki using mediawiki and I’d like some help ensuring the server and mediawiki is safely setup before I start sharing it publicly. I installed it on Vultr using the mediawiki app from the Vultr Marketplace. Are there any things I should ensure before publicly sharing the link?

Some things I’ve done so far:

  • I disabled password login to the server so its only possible to login via ssh

  • I made it so I have to approve of any edits to the wiki

  • I still haven’t enabled uploads of files because I want to ensure I only allow jpeg\png uploads.

I’m relatively new to running servers so any tips are highly appreciated.

    • xnx@lemm.eeOPEnglish
      21·
      1 year ago

      ELI5? 😅

      The install section of naxsi is a whole lotta stuff I’ve never touched before

      • I eat words@group.ltEnglish
        1·
        1 year ago

        sorry, this is kinda like a firewall, but protecting websites, so many vulnerabilities are filtered out. it does not protect you 100% percent (nothing does). it might be hard to setup, in that case there is an option to use waf as a service, i.e. - cloudflare has such offering, maybe there are others as well. i have looked into vultr - they seem to offer only a “usual” type of firewall, not http/application based.

  • Decronym@lemmy.decronym.xyzBEnglish
    51·
    1 year ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HTTP Hypertext Transfer Protocol, the Web
    HTTPS HTTP over SSL
    IP Internet Protocol
    SSH Secure Shell for remote terminal access
    SSL Secure Sockets Layer, for transparent encryption
    VPN Virtual Private Network

    4 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

    [Thread #74 for this sub, first seen 23rd Aug 2023, 08:05] [FAQ] [Full list] [Contact] [Source code]

  • Illecors@lemmy.cafeEnglish
    1·
    1 year ago

    I disabled password login to the server so its only possible to login via ssh

    Phrasing is a bit strange. Does this mean ssh can only be used to login with a key? If so - great!

    Since you’re using an “app” - not sure there’s much we can help you with. The control has been ceded to the maker of said app.

    I would normally set up some limits on the firewall and change the ssh port so logs are less polluted, not sure it’s possible for you.

    • xnx@lemm.eeOPEnglish
      1·
      1 year ago

      Yeah its only possible to login with a key.

      What limits would you set on the firewall?

      From the bit I’ve read people usually say changing the ssh port is mostly “security theatre” is this not fully true?

      • diminou@lemmy.zipEnglish
        3·
        1 year ago

        For the limit : basically you need to ask yourself how many connection someone if able to do in a second to your server. As an example, my limit is always 15. A bit high but I’m sure I’m not blocking a legitimate one (either from myself or someone else)

        For the ssh port : it’s true, but trust me you’ll be happy to change for something random like 5927 because you’ll have far less bit trying to connect or probe your ip, thus your logs won’t be cluttered!

      • Illecors@lemmy.cafeEnglish
        1·
        1 year ago

        It would be security theatre if it was done for security. I’m not doing it for security, though - it’s for my sanity when checking the logs. Unrestricted SSH simply attracts too many bots and the failed logins make it impossible to quickly grasp a picture of what’s happening.

        In regards to limits - this is my rule file for iptables on my lemmy instance:

        *filter
:INPUT DROP [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:LOG_DROP [0:0]
:LOG_ACCEPT [0:0]

-A INPUT -p tcp -m tcp --dport 22 -m state --state NEW -m recent --set --name DEFAULT --mask 255.255.255.255 --rsource
-A INPUT -p tcp -m tcp --dport 22 -m state --state NEW -m recent --update --seconds 600 --hitcount 20 --name DEFAULT --mask 255.255.255.255 --rsource -j LOG_DROP
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -m state --state NEW -m recent --set --name HTTPS --mask 255.255.255.255 --rsource
#-A INPUT -p tcp -m tcp --dport 443 -m state --state NEW -m recent --update --seconds 600 --hitcount 600 --name HTTPS --mask 255.255.255.255 --rsource -j LOG_DROP
-A INPUT -p tcp -m tcp --dport 443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A INPUT -j LOG_DROP

-A LOG_ACCEPT -j LOG --log-prefix "[ACCEPTv4]: " --log-level 7
-A LOG_DROP -j LOG --log-prefix "[DENYv4]: " --log-level 7
-A LOG_ACCEPT -j ACCEPT
-A LOG_DROP -j DROP
COMMIT

        This is very much a WIP, I’m going to implement some ddos protection as soon as I get some spare time.

        • xnx@lemm.eeOPEnglish
          1·
          1 year ago

          Could you explain a bit of what these are doing and why you decided on these rules?

          Also, isn’t bruteforcing an SSH key near to impossible?

          • Illecors@lemmy.cafeEnglish
            1·
            1 year ago

            There are 2 extra chains - to log a connection and accept it, and to log a connection and drop it. I’ve only used log and accept for testing.

            The default action on input chain is also changed to drop.

            SSH port gets connection attempts counted - 20 connections within 10 minutes from the same IP and it goes to log and drop. I could just drop it, but for now I feel immense satisfaction knowing that some bot is waiting for timeout instead of attempting the next username/pass.

            I’ve tried a similar thing with https because lemmy.world was dosing me. It did work, but I’ve now commented it out since Lemmy software has become more robust. Lemmy.world still sucks from my, as an instance owner, perspective, but it no longer bombards me periodically.