Re:How to secure your new VPS: a step-by-step guide
by akerl_ on Monday October 21, 2024 @10:16PM
(#41910536)
Far more VPSs are compromised through local VM attacks than provider attacks.
This is a bit like saying "When you're temping your chicken, always remember that your grocery store could be putting arsenic in it at the store". Yea, that's true. But the average consumer gets sick far more often from mistakes in the kitchen than mistakes in the grocery store.
Re:How to secure your new VPS: a step-by-step guide
by gjsman-1000 on Monday October 21, 2024 @10:17PM
(#41910545)
The person in question on HN was planning to self-host email. Sure, if you don’t want Google or Microsoft in particular reading it, I get it. But if you think nobody can read it now, that’s a major (potentially life threatening) mistake. Gmail might actually be safer in many circumstances.
Re:How to secure your new VPS: a step-by-step guide
by aspenmayer on Monday October 21, 2024 @10:59PM
(#41910790)
If you don’t want Google or Microsoft reading your email, Proton would be better still than Gmail, wouldn’t it?
Re:How to secure your new VPS: a step-by-step guide
by panarky on Tuesday October 22, 2024 @12:32AM
(#41911224)
If any of your recipients are using Google or Microsoft then they already have your email whether you use Proton or not.
Re:How to secure your new VPS: a step-by-step guide
by remram on Monday October 21, 2024 @11:35PM
(#41910964)
I wouldn't say meaningless, no. If your provider is not too diligent about checking subpoenas, they will let a sophisticated targeted attacker in eventually. If your SSH password is weak, you will let any and all script kiddie in within the hour.
All of your VPS security is meaningless compared to your VPS provider’s security, the security imposed on the employees of the VPS provider, the security of your VPS account password, and their susceptibility to faked subpoenas and faked emergency data requests.