• 3 Posts
  • 157 Comments
Joined 10 months ago
cake
Cake day: February 2nd, 2026

help-circle

  • First off: you’ve come a long way. Great setup, keep it up!

    As others have said, I’d reduce your reliance on Proton. I’d particularly ditch their password manager in favour of something like KeepassXC and combine it with Syncthing (which you’re already using) in order to keep your passwords out of the cloud, but synced between your devices. Always think in terms of blast radius: if an attacker gets access to your Proton account (either because you fuck up or they do), they will have access to anything that’s in there. Having your e-mail + pw manager there increases blast radius dramatically and allows not only for access to, but full takeover of your accounts in case of a breach.






  • IratePirate@feddit.orgtoPrivacy@lemmy.ml•Vent about bank apps
    link
    fedilink
    arrow-up
    26
    arrow-down
    2
    ·
    edit-2
    5 months ago

    some people live in the European hellhole

    That’s rich, coming from a country that can burn hundreds of billions of Dollars in Iran for abso-fucking-lutely nothing, but is somehow unwilling to give its own citizens universal health care or free access to higher education! 😄 But then again, crushing debt and lack of access to education / higher-paying jobs help make sure there are always fresh “volunteers” for the illegal wars of the oligarchs bringing the world democracy and free’m and shit, right?


  • IratePirate@feddit.orgtoPrivacy@lemmy.ml•Private music?
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    5 months ago

    I got other people on my network who prefer faster internet speeds over privacy, sadly. And I dont wanna be rude and just force them to do something they don’t want to do. (Even if it’s for the greater good)

    This would not impact internet speed for anyone else on your network. Whether they’re connected via Ethernet or WiFi, they’d have the same speeds as before.

    As for a Wireguard connection tunnelling in from outside, it has so little overhead that it does not meaningfully impact speed or latency (I’d know, I use it every day).

    Also, you can set up the tunnel as a split tunnel. This means that

    • only traffic directed at your homeserver with the music server goes through the Wireguard tunnel while
    • any traffic directed at the open internet does not go through Wireguard, i.e. zero speed or latency penalty.

    Also attaching it to my router won’t work when I’m out travelling or away from home.

    I’m not sure what you mean by “it” here. Feel free to fill in the blank.





  • I’ve started working on something very similar ( Client -> Wireguard -> homeserver -> Mullvad -> Internet), but didn’t get too far and saved the project for later. IIRC, I had issues defining more clearly in the post-up / post-down hooks which traffic was supposed to go where. Upon bringing up the tunnel to Mullvad, I’d lose SSH access instantaneously. I’ll watch this thread closely and contribute once I get around to tackle the issue sometime this summer.





  • //Edit: terminology improvements

    One per service. Not just because it’s easy, but because it allows you to minimise blast radius. If you’re running one DB DBMS per container service and one container gets compromised, only that one DB DBMS is compromised. With one centralised DB DBMS for all containers, a breach of one container means access to the data of all containers that use this without the need for any lateral movement.