this post was submitted on 23 Aug 2023
14 points (100.0% liked)

Selfhosted

40152 readers
512 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
14
Need help ensuring my public mediawiki is safe before launch (lemm.ee)
submitted 1 year ago by xnx@lemm.ee to c/selfhosted@lemmy.world
21 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] saint@group.lt 1 points 1 year ago (1 children)

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.

[–] xnx@lemm.ee 1 points 1 year ago (1 children)

Ah ok thanks for the info! Do you know if vultrs firewall would make installing fail2ban redundant?

[–] saint@group.lt 1 points 1 year ago (2 children)

if you configure ssh access only from your home ip - then fail2ban is not needed.

[–] xnx@lemm.ee 1 points 1 year ago

Oh perfect thanks

[–] Haui@discuss.tchncs.de 1 points 1 year ago (2 children)

But if your home ip ever changes, you‘re fucked. I would never do that. Pubkey is the way.

[–] SheeEttin@lemmy.world 2 points 1 year ago (1 children)

Method of authentication doesn't matter if there's a pre-authentication vulnerability: https://thehackernews.com/2023/02/openssh-releases-patch-for-new-pre-auth.html

Instead of exposing multiple services, I would recommend just one VPN for remote access. Less attack surface.

[–] Haui@discuss.tchncs.de 1 points 1 year ago

Thats how I do it. But I also have physical access so if the vpn fails I don’t get locked out.

[–] saint@group.lt 2 points 1 year ago (1 children)

usually i add more than 1 ip and also vultr firewall can be managed to change ip. tailscale can be used as well. there are options!

[–] Haui@discuss.tchncs.de 2 points 1 year ago

That’s good! Had me worried there.