4 ms·
One thing the article glossed over is the SSH key. I set this up for remote access to a computer behind a NAT router that does not allow any incoming connection
by NelsonMinar 11y ago
One thing the article glossed over is the SSH key. I set this up for remote access to a computer behind a NAT router that does not allow any incoming connections at all. For that to work robustly in case of a reboot, the private ssh key used by that computer must have no passphrase. That always makes me nervous, I ended up setting up the public computer side of this with a special user account that was as locked down as I could make it. All the ssh tunnel will do is forward port 2200 on the public machine to my computer's ssh port. Works great!
- Piskvorrr 11y agoOr you could use a SSH agent (Pageant, ssh-agent): you enter your key passphrase once when starting the agent, and it handles the key auth on your behalf.
- e40 11y agoWhy is this getting downvoted? It's clearly the right thing to do.
- NelsonMinar 11y agoHow do I enter the passphrase when the computer behind the firewall reboots?
- Piskvorrr 11y agoAh. Now that's a problem I have no solution for - only the same workaround as you describe (you have taken one more step than I did by having a dedicated host for the SSH connection, instead of just an account - with today's virtualization, this is easier than ever :)).