-
-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh.chat: Deploy Tor hidden service endpoint #375
Comments
Not a bad idea, I'm happy to host it on the same instance. Do you have a fav guide? Biggest downside is latency is probably gonna be gross. |
If you don't need advanced features like vanguard, it's relatively easy. Just skip step 1 of this guide: https://community.torproject.org/onion-services/setup/ |
You should be able to start the onion service without shutting down the ssh-chat service. This should preserve chat logs and uptime. |
Awesome, I'll add it to the TODO list. Also IIRC there's a Go-native implementation of onion services somewhere, wonder if I could embed it as a native feature of ssh-chat easily, will look into it briefly. |
IMHO: Not worth it. Adding additional code can compromise software security. Tor is easy to interface with existing services, so might as well use that. |
It's more of a balancing act of how much maintenance things require for me, fewer moving pieces (ie. keeping one binary up) is always easier than a rube goldberg machine of systemd services. But yes, I'll keep that in mind. |
True. However, when you use the official package provided by the Tor Project, you get the backing of an organization that maintains the software, fixes vulns and does research on the latest threats to the tor network. Feel free to do however you like though, as I don't know how your infrastructure is deployed. |
shazow: I made a typo in my recommendation! Strike out the modified lines! Having two services listen on the same port will mess up your server! |
@nya-furball Welcome back! |
UwU |
It's very easy to do...
Add lines to /etc/tor/torrc
Then restart tor daemon and If you want to make it tor-only, make the --bind=127.0.0.1:[port] ...don't use port 22. That's for real ssh sessions. Plus, you can't reverse ssh tunnel below port 1001 without root... Pick a number above so you don't have to expose root. ...make sure client has torsocks installed. If you use the same ssh key, you just gave away your identity, so... |
@camosoul That's helpful, thanks. :) Just need to get around to it... |
Is there any interest in offering ssh.chat as both a clearnet server and hidden service? If there is, I am willing to help out with setting up stuff!
The text was updated successfully, but these errors were encountered: