3 ms·

If you don't want your data to be accessible to "various agencies", don't share it with corporations, full stop. Corporations are obliged by law to make it avai

by nine_k 2y ago

If you don't want your data to be accessible to "various agencies", don't share it with corporations, full stop. Corporations are obliged by law to make it available to the agencies, and the agencies often overreach, while the corporations almost never mind the overreach. There are limitations for stuff like health or financial data, but these are not impenetrable barriers. I would just consider all your hosted data to be easily available to any security-related state agency; consider them already having a copy.

immibis 2y ago
That depends where it's hosted and how it's encrypted. Cloud hosts can just reach into your RAM, but dedicated server hosts would need to provision that before deploying the server, and colocation providers would need to take your server offline to install it.
- nine_k 2y ago
  Colocated / Dedicated is not Cloud, AFAICT. It's the "traditional hosting", not elastic / auto-scalable. You of course may put your own, highly tamper-proof boxes in a colocation rack, and be reasonably certain that any attempt to exfiltrate data from them won't be invisible to you. By doing so, you share nothing with your hosting provider, you only rent rack space / power / connectivity.
  - doublerabbit 2y ago
    And this is why I colocate, because all the data that hits my server is my data. Sure I do have an AUP/T&C but without proper warrant no one is allowed to touch my server. Case is monitored if it's opened. Encrypted on start-up, USB disabled. I just wished I had my own /24.
    - immibis 2y ago
      At least you can get your own /48, at least if you're under RIPE. You should only do it if you expect to multihome though, or you're doing some experimentation that absolutely needs a PI address. Please don't pollute the default-free zone just for no reason.
fulafel 2y ago
There's much variation by jurisdiction. Eg US based big-cloud companies would seem more risky here if you're from a country with traditionally less invasive (and less funded) spooks.

by nine_k 2y ago

immibis 2y ago

That depends where it's hosted and how it's encrypted. Cloud hosts can just reach into your RAM, but dedicated server hosts would need to provision that before deploying the server, and colocation providers would need to take your server offline to install it.

nine_k 2y ago
Colocated / Dedicated is not Cloud, AFAICT. It's the "traditional hosting", not elastic / auto-scalable. You of course may put your own, highly tamper-proof boxes in a colocation rack, and be reasonably certain that any attempt to exfiltrate data from them won't be invisible to you. By doing so, you share nothing with your hosting provider, you only rent rack space / power / connectivity.
- doublerabbit 2y ago
  And this is why I colocate, because all the data that hits my server is my data. Sure I do have an AUP/T&C but without proper warrant no one is allowed to touch my server. Case is monitored if it's opened. Encrypted on start-up, USB disabled. I just wished I had my own /24.
  - immibis 2y ago
    At least you can get your own /48, at least if you're under RIPE. You should only do it if you expect to multihome though, or you're doing some experimentation that absolutely needs a PI address. Please don't pollute the default-free zone just for no reason.

fulafel 2y ago

There's much variation by jurisdiction. Eg US based big-cloud companies would seem more risky here if you're from a country with traditionally less invasive (and less funded) spooks.