𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 
  • 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2022

help-circle

  • Is your server a dedicated server, or a VPS? Because if it’s a VPS, you’re probably already running in a VM.

    Adding a VM might provide more security, especially if you aren’t an expert in LXC security configuration. It will add overhead. Running Docker inside Docker provides nothing but more overhead and unnecessary complexity to your setup.

    Also, because it isn’t clear to me from your post: LXC and Docker are two ways of doing the same thing, using the same Kernel capabilities. Docker was, in fact, written in top of LXC. The only real difference is the container format. Saying “running Docker on LXC” is like saying “running Docker on Docker,” or “running Docker on Podman,” or “running LXC on Docker”. All you’re doing is nesting container implementations. As opposed to VMs, which do not just use Linux namespace capabilities, and which emulate an entirely different computer.

    LXC, Podman, and Docker use the underlying OS kernel and resources. VMs create new, virtual hardware (necessarily sharing the same hardware architecture, but nothing else from the host) and run their own kernels.

    Saying “Docker VM” is therefore confusing. Containers - LXC, Podman, or Docker - don’t create VMs. They partition and segregate off resources from the host, but they do not provide a virtual machine. You can not run OpenBSD in a Docker container on Linux; you can run OpenBSD in a VM on Linux.



  • Nope! No security concerns!

    But, seriously, if one machine in the Wireguard network is compromised, attacks can be launched on any other machine in that Wireguard subnet. At that point, whether you’re running Wireguard or not is irrelevant.

    For your specific setup, the weak point is the VPS. Everything is good, but if someone successfully beaks into an account on your VPS with access to the Wireguard device (and almost nobody goes through the effort of constraining network devices by account, and of course there’s always root) they can launch attacks on any machine in the WG subnet.

    It’s a little better if you’re running containers and they’re secure, but even then there are security considerations with containers. Still, that’s about the best you’re going to get: anything listening to any external internet port is running in a container with no resource runtime, and those ideally each only have limited access to the ports in the WG subnet that they need. Eg, something like:

    In your diagram, your VPS is just a gateway. If the only way to log into the VPS is over WG; and if the reverse proxy is running in a locked-down container; then this is about a secure as you can make it and still allow public access.

    Or: if the only way your VPS is at all accessible is over WG – all clients have to be connected to it via VPN – then it’s reasonably secure as long as no client is compromised. Then your remote devices become the weak points.



  • I miss the old days, before you had to worry about spam.

    I’m not OP, and I have everything set up fine now; Mailcow would replace what I currently have with the same software components, so I don’t see any value there - for myself.

    Something like Maddy is completely at odds with the Unix philosophy, and yet I’ve fought enough with postfix to dislike it enough to want to try an all-in-one. I dread the DKIM setup, though; that took so much time, and the mail server configuration wasn’t the hard part. Maybe now I’ve got it configured for my domains, switching email server software will be easier.







  • DMCA is widely abused; it’s a knee-jerk corporate reaction, and by now most DMCA notices are probably being sent out by LLMs. Very likely, a substantial percentage are not even valid - either targeting content that the requester has no claim to, is falsely identified, a form of harassment, or targeting content which is justifiably and legally fair-use.

    Hosting services don’t even try to validate these claims. You assume OP is asking for piracy reasons; we have no way of knowing, but I’m always going to side with the content providers against the gross abuse of DCMA by media corporations.



  • I don’t know that I can answer your question, sorry, but something you said confuses me.

    • file storage/syncing from a central server (so Syncthing is out) … While working absolutely fine for sync between different devices (have it in use in a different scenario), the peer-to-peer nature is unsuitable for what I’m looking for

    Why? I think you missed describing a requirement, because there’s no reason SyncThing can’t do “for syncing from a central server.” Do you mean one-way, or one-to-many, or what? What, exactly, doesn’t SyncThing do that you need?

    I believe SyncThing is not the right tool in many scenarios, but I don’t understand these bullet points.

    For one thing, SyncThing is only peer-to-peer if you set it up that way. You can absolutely define a “master” simply by only connecting the “clients” to the master. It’s an utterly arbitrary distinction, but the clients won’t know about or communicate with each other unless you explicitly pair them with each other. This is how I have our phones set up: each one is paired to the central server, but neither is an introducer nor knows about each other. We have one directory that the server has shared with both phones, and several directories that the server shares only with one or the other phone. I even have the server connected and sharing all of the directories with a second, backup server that neither phone knows about.

    Again, I’m not pimping SyncThing; it has weaknesses, the biggest one being any lack of sophisticated merge ability. I wish it had a plugin system where, for each for type, in case of conflicts it would call out to some external merge program; rather than just throwing up it’s hands and going, “well shucks, guess I’ll just spam a bunch of sync conflict files”. And it can be annoyingly slow recognizing changes and syncing; it would be a terrible choice for any sort of pair programming file sharing.

    But what problems have you encountered with it, for your case?