Selfhosted

39435 readers

4 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Self hosting on desktop: how to secure self hosted apps from proprietary desktop apps? (reddthat.com)

submitted 1 year ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

Hello friends, I am considering self hosting on my desktop computer, which already has gentoo Linux installed. But my concern is that my regular desktop use could compromise the security of self hosted applications, which tend to handle private user data.

What can I do to secure myself against this threat?

For example, browsers on their own are a security nightmare. You are running arbitrary remote scripts, and there's no telling the extent of damage they do (most websites out there doing extensive tracking).

What can I do to secure my self hosted applications while running them on the same machine? Is there something I can do to somehow isolate browsers and other sketchy applications from the damage they could possibly do?

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago)

Maybe just don't run your services under your regular user account?

Create one or more new user accounts and run them that way. Make sure not to give your regular user account any access to the data in the new accounts.

That doesn't stop all attacks: side-channel attacks (Spectre?) can still happen, and your machine can for example still run out of memory and break your services that way, but it's a solid start.