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!
view the rest of the comments
In the end it depends on your risk profile and adversary model. Usually it's not a good idea though. Why not have an SSH tunnel to the network/machine and use port forwarding to forward the RDP connection? Or why not use SSH for remote access, period?
My work's network is pretty locked down, which is why I'm trying to think of other solutions that would work.
Hey man, so I've been thinking about this and doing a lot of reading since I read your comment... Question: what makes an SSH tunnel any more secure than an SSL connection through a browser? I only have port 443 opened on my home network for reverse proxy and wouldn't want to open anything more to the internet. Am I missing something fundamental in terms of security? I would definitely like to understand this more.
The nice thing about an SSH tunnel is that it only exists when you create it, on the fly, per use, with your SSH credentials. And it is only accessible if you possess an authorized private key. An SSL connection through a browser doesn't fill the same role. SSL provides privacy and security in the communication between server and client. It doesnt have authentication built in. If you are accessing through a web browser you are probably talking to a web server, but SSH allows you to tunnel any protocol (web, rdp, whatever) forwarding traffic, encrypted, across a chosen port.
Edit to add a bit more: attack surface. SSH is a very robust and heavily used protocol with well tested implementations. Other solutions involving the web are probably involving software stacks with layers of configuration, more rapid iteration to add features and therefore a higher probability of vulnerabilities existing or being introduced in updates. Is this consideration relevant to your use? Probably not, =P but you asked about what might differentiate these two approaches from a security standpoint.
Ah perfect! Exactly what I was looking for! Thank you so much for that explanation. Definitely trying to understand more about security and your explanation just made something click in my brain :)