view the rest of the comments
Selfhosted
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!
Now I know this is being done with encryption, but an open tunnel direct to your non dmz-ed system, is just begging to be hacked, and it will be, without a shadow of doubt.
In what sense is this "opening a direct tunnel?"
I don't think you really understand what's going on here; or otherwise, I don't.
I've used BOINC without issue for over a decade.
As far as I know, the BOINC client just pulls down new data for processing when each batch of work is done. There's no pushing and no open tunnel or port. The software risk would be malicious code in a particular project (e.g. if it said it was folding proteins but actually mined bitcoins). I hope there's some vetting of project code.
The other risk is hardware (especially CPU and RAM) running its lifetime down more quickly because of the continual heavier usage.