• 3 Posts
  • 14 Comments
Joined 2 months ago
cake
Cake day: September 27th, 2026

help-circle

  • Your end goal, friend, is noble, and I don’t mean to discourage you or gatekeep. And yet I must strongly advise you to slow your horses before you squander what I’d call your “social capital”, i.e. the willingness of the people close to you to follow your recommendations and try out new things. If they find their user experience greatly lagging behind what they’re used to, not only will they return to the services they were using prior to your suggestion: they will also be less likely to listen to you in the future and meet alternatives with skepticism, if not hostility. (“I’ve tried it and all this other stuff doesn’t work…”)

    Thus, you need to make sure that they have an excellent first experience with whatever you throw their way. As a tinkerer, tech enthusiast, privacy advocate, or whatever you want to call yourself, you’re likely willing to accept a great amount of jankiness, pain, and lack of feature parity because you feel you get something more valuable in return. But that is not how most people use computers. Most people do not care about privacy, digital independence or any of the things you may cherish; they want things to “just work”.

    And, to put it brutally bluntly (sorry!),

    Like I think I’d need tailscale and docker (still dont get what docker really is)

    this part alone tells me your solution is unlikely to “just work” for them. These are some basic skills to have if you want to try and compete with a billion-Dollar company and the convenience it provides to your friends.

    So, my advice is this: don’t aim for “perfect”, aim for “better”. And basically anything is better than using FB Messenger, Whatsapp, Discord or whatever they may be using. Either go for one of the large public Matrix nodes (Matrix.org is unlikely to go down any time soon…) or move your comms to Signal messenger. Both may not be fully under your control (Signal is centralised, and Matrix nodes might be closed or defederated), but they’re e2ee and so professionally managed that your friends might actually enjoy them, use them on a day-to-day basis, and even pull other people over. That way, you’re also building social capital, so that once you’ve obtained the skill to run your own and get it to the level of polish it needs to have, they’ll be willing to follow you there too.

    (If this posting sounds like I’ve learnt this the hard way, that’s because I have. Things are fine now, though: almost my entire social graph is reachable via Signal, and I’m preparing to self-host my own comms.)







  • Feel free to elaborate. ;) I don’t mind ditching folders. The question is: how do I get at said metadata with the least amount of manual effort, how do I make sure that it’s accurate (sifting through thousands of files is not fun), and how is the metadata stored - particularly so that does not lock me into one application that can only understand its own metadata scheme, and once it dies or I want to switch to a different one, I lose all the work I’ve put into curating my collection. That’s why I was considering folders as an option: they are a software-agnostic way of organising my library.




  • LewdLemon@sh.itjust.workstoSelfhosted@lemmy.world•Backup
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    29 days ago

    I’ve got your exact setup:

    • running immich (and other services with valuable data) at home (on OMV!)
    • backup server at family member’s house
    • regular backups from here to there through Wireguard tunnel with Borgbackup

    AMA!

    I don’t want a compromised device on the family member’s network to compromise mine

    If with “mine” you mean the pi Zero, I wouldn’t worry too much about that. Just configure the pi’s firewall to drop all traffic from the LAN (they have no business with this device anyway), except any incoming traffic from the router on the Wireguard port.



  • Thanks for your detailed reply and expertise! I really appreciate it!

    First question you have to ask yourself is so what?

    You’re right to call out my lack of threat modeling. I am aware that the “cost” of what I’m planning here likely outweighs the actual risks. That’s a deliberate choice though: one of my objectives in homelabbing is to “learn how the big guys do it”, i.e. learning and implementing, bit by bit, networking and security best practices.

    That said,

    • all of my drives are (LUKS) encrypted (although this will only help against evil maid attacks physically stealing my disks, since data is only encrypted at rest, not while the server is in operation)
    • I do have some CPU monitoring in place
    • I have applied the principle of least privilege (as far as I can see at least)
    • I have set up an off-site backup server running (although I need to improve automation and deduplication; I’ll probably go with Borg here)

    Thank you also for pointing me towards OWASP Docker cheat sheet! I didn’t know this resource yet, although I seem to have found others that said the same thing. I already have in place:

    • no docker socket exposed to services
    • user set for every service that didn’t give me a headache doing that (some assume root and won’t accept setting a user)
    • username remapping is active
    • all containers have their caps dropped and selectively only put those back in which they need
    • I expose almost no container ports, and only those necessary; instead, communication with the containers is handled on my reverse proxy’s network (i.e. via the internal docker network)
    • privilege escalation is disabled

    I have played around with rootless docker (again, stubborn containers assuming root prevented me from going all-in) and considered Podman, although just putting containers in a VM looks like a more frictionless route to me.


    All things considered, your advice seems to be:

    1. to first consider whether I actually need all this security. I really don’t, yet I want to learn how to set it up anyway.
    2. to first explore and all other hardening avenues. I have, to a certain degree, and beyond that run into brick walls.

    If I might exhaust a little more of your time, I’d be curious how you judge the next step I’ve suggested: splitting duties between separate servers, thus segmenting public from private physically, or going the virtual route (again, by splitting into a public and a private VM and separate them through strict software firewalling).


  • Thanks for your input. It is correct that a lot of ISPs/consumer grade hardware is poorly maintained. Mine is a rare exception, however: I’m running an AVM FritzBox, which are somewhat famous for still receiving updates even after 10+ years on the market. They have only recently pushed a security update my way, so I’m good enough on that front - for now.

    I shall consider a firewall in the future though.

    I hope part of your hardening SSH is changing the port number!

    I used to do that, but then realised that doing so will do very little. Scanning all possible ports is a matter of seconds, and SSH (unlike Wireguard) will signal to a potential attacker that it’s listening on port X instead of just remaining silent. In other words: in my eyes, it’s security by obscurity and will have very little effect.

    What I have done to harden SSH is:

    • set up pubkey authentication and disable password authentication
    • disable root login
    • not expose my SSH port publicly; it is accessible only from my LAN and through Wireguard

    I have also tried out IP whitelisting (which may harden my setup against attacks from the LAN), but found it may be overkill for now. I might turn it back on just for shits and giggles.