HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
shellhub-io
shellhub
Go2020–2020
shellhub-io / shellhub

shellhub

:computer: Get seamless remote access to any Linux device. Centralized SSH for the edge and cloud computing

2Distinct people
2Mentions
0Explicit recommenders
2.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:computer: Get seamless remote access to any Linux device. Centralized SSH for the edge and cloud computing

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2020-01-27 20:45:48 UTC to 2020-01-27 22:51:39 UTC.

012020-01-27 20:00:00 UTC to 2020-01-27 21:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 27, 20:002020-01-27 21:00:00 UTC to 2020-01-27 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 27, 21:002020-01-27 22:00:00 UTC to 2020-01-27 23:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 27, 22:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 27, 20:002020-01-27 20:00:00 UTC2020-01-27 21:00:00 UTC110
Jan 27, 21:002020-01-27 21:00:00 UTC2020-01-27 22:00:00 UTC000
Jan 27, 22:002020-01-27 22:00:00 UTC2020-01-27 23:00:00 UTC101

What Hacker News says

2 sources
This is interesting, but how does it work? By leveraging a STUN/TURN server? Can we connect on port 22? Actually, there is this link in the subtitle (and in the readme, but only mentions "getting started", now "how does this work"): https://shellhub-io.github.io/ this should probably be the story link. So, short answer to my question (though I had to read https://github.com/shellhub-io/shellhub/commit/fb0ebf10b1270... to understand it, the website wasn't enough): * You host a TURN-like server somewhere * You locally host an ssh server (see the above commit: using docker) * When you ssh to the local server, the TURN server is contacted, and performs the handshake; your local server proxies to the remote one on the right port This is an interesting proof-of-concept, but: * I wish people would deploy ipv6 without (or with minimal) firewalls
Read the rest
instead * As with all TURN, doesn't work with symmetrical NATs * This is a bit overkill. If I could ssh into the TURN server and have it reply with the right ssh command, it would work as well (need to be quick) Given the above, this could be built into ssh: specify a TURN server (or plain ssh host) to negociate a port and have the client & server perform the handover. The way I do NAT traversal usually is to setup a reverse tunnel between the target sshd and another server (initiated by the target host), which I then proxy/jump on with `-p`. Obviously this uses some of the server's bandwidth, hence my proposed offer to add something like TURN negotiation on the server. The intermediate server doesn't even need to be aware of this, if you can execute arbitrary commands. I wish more applications were compatible with something like this. The Internet really is broken if we have to jump trough these hoops to get any p2p going. There might be a way to do it in a way that's transparent to the application, but we might need a new TCP for this. I wonder if Yggdrasil or GNUnet offer to solve that kind of issues over the current TCP network (making a VPN of sorts between the computers, but not firewalled/NATed).
In ShellHub enables teams to easily access any Linux device behind firewall and NAT

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.