117
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jul 2023
117 points (97.6% liked)
Selfhosted
40219 readers
391 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 1 year ago
MODERATORS
It’s not as detectable as you think. One of the major things most VPS companies tout, is that the data is fully encrypted and private. So they aren’t scanning the files, or the running processes, or anything else about what is being done with the server.
So unless something external to the company is provided, which acts as proof, they won’t shut things down.
This is true for most providers but not the big big ones. Ask me how I know ;)
I'm curious if leaving the data-at-rest encrypted on the filesystem using something like EncFS would mostly solve this. (EncFS encrypts all the files on disk and gives you a mount point to access the corresponding cleartext filesystem)