Selfhosted

51078 readers

1177 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

What privacy related configurations should I be mindful about when deploying in a VPS? (lemmy.pe1uca.dev)

submitted 2 years ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I have a small VPS running a few scripts and some personal projects without any private information (just the keys for the services needed).
I want to expand it to selfhost more stuff like Google photos alternative, knowledge DB, git, etc., but I'm not sure how is my data protected inside a VPS.
There was a post mentioning everything is visible to the provider via the hypervisor, so I was wondering if an encrypted volume would make no difference for protecting any data uploaded there.

Am I being too paranoid? Or should I be investing in a small physical server?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 2 years ago

Also worth mentioning that modern CPUs support VM-level encryption, so that even the host can't see what's inside the VM at all. The RAM is transparently encrypted by the CPU, so unless the provider goes to some pretty extreme (and expensive) length to extract the keys from the PSP for a regular random nobody, it's barely worth thinking about. See: https://www.qemu.org/docs/master/system/i386/amd-memory-encryption.html

As long as you don't get into legal troubles the provider has better things to do than ruin their reputation with big corporate customers.

Encryption at rest never hurts however. But the runtime may also be encrypted and really private. Lemmy is very public anyway, I wouldn't worry much.