• 0 Posts
  • 64 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle




  • I’m not concerned about it personally, but you are putting a lot of trust in them as a 3rd party service provider. It’s up to your specific risk profile if that’s acceptable risk or not.

    The alternative would probably be self hosting a vpn yourself with dyndns to handle ip address resolution. I’m biased (I have a professional networking background) but I don’t think it’s that much harder to setup either. But then I’m also a hypocrite and don’t self host anything anymore.

    There’s also a valid argument to be made that doing it yourself is riskier because novices make mistakes. I don’t think this is too big of a concern personally - it’s not like you’re rolling your own cryptography.










  • Docker is fine for turnkey applications. Mounting external storage that persists across containers is a feature that enables that pattern.

    Running Docker in a VM is also fine and has potential advantages. However I agree that it’s probably overly complex for many people.

    I’m confused what you’re trying to accomplish here. Are you trying to make it look like the traffic is coming from your VPS for some reason? Nginx (amongst others) can reverse proxy tcp traffic.






  • Isn’t this just CRL in reverse? And CRL sucks or we wouldn’t be having this discussion. Part of the point of cryptographically signing a cert is so you don’t have to do this if you trust the issuer.

    Cryptography already makes it infeasible for a malicious actor to create a fake cert. The much more common attack vector is having a legitimate cert’s private key compromised.