Difference between revisions of "SSH - tunnels, X forwarding"

From Helpful
Jump to: navigation, search
m (X11 forwarding request failed on channel 0)
m (PuTTY X11 proxy: wrong authorisation protocol attempted)
Line 514: Line 514:
  
 
-->
 
-->
 
===PuTTY X11 proxy: wrong authorisation protocol attempted===
 
 
I got this when the ssh server's system disk was full,
 
which meant the negotiated secret couldn't be stored in .Xauthority.
 
 
There are other reasons.
 
  
 
===remote port forwarding failed for listen port===
 
===remote port forwarding failed for listen port===

Revision as of 16:35, 30 September 2021

Security related stuff.

Practical


Theory / unsorted

how to do a login system badly
how to do encryption badly
Disk and file encryption notes
These are primarily notes
It won't be complete in any sense.
It exists to contain fragments of useful information.


TCP tunnels

Basic description

SSH tunnels mean that,

  • on top of an established a SSH connection,
  • you make one side listen to a specified port (you choose which side, and which port)
-L is "once the SSH connection is established, listen from the connecting client's side"
-R is "once the SSH connection is established, listen at remote/server side"
  • when a regular TCP connection is made to that listening port
it will be carried to the other end of that SSH connection (securely)
and from that other host make a new, non-secured (!) TCP connection, to the a host and port you also specified.


Why that is useful is not immediately obvious, so...

Introduction by example

...here's some introduction via real uses I've had for it:


  • Say I have a database-exploring GUI on my laptop, and a database server that has SSH open but is otherwise firewalled
on that laptop I might do (e.g. for postgresql, so port 5432):
ssh -L 5432:localhost:5432 dbserver.example.com
so now, when something connects to my laptop's port 5432, like my own GUI, it actually goes to what on the the SSH server's networking side is localhost:5432
As far as the dbserver is concerned, it's seeing a connection from its localhost. Which also means
my laptop's doesn't need to be trusted (the database never even sees its IP)
the database server doesn't need to listen to its LAN at all, and can stay tightly firewalled


  • I sometimes want to remote-desktop to an internal Windows server at work.
And have an internet-exposed linux server at work, on the same (V)LAN as that windows server
similar idea as the last in that I get into a SSH server at work
different in that I now tell that connection to go to that windows server (private 192.168.something IP)
ssh -L 3389:192.168.1.200:3389 ssh.work.example.com
note that on the work side, that's still an private network - unroutable beyond that subnet


Considering direction of SSH connection and/or tunnel

  • I have a monitoring web-app on a work server that I want to check from home, but it's intentionally firewalled beyond that work LAN
In theory, we could use the above, but to get a HTTP connection through requires multiple steps, so is more awkward and fragile
Instead...
I have a ssh server on my home broadband, so I have a simpler option. While I'm still at work, on that work host:
ssh -R 5000:localhost:5000 ssh.home.example.com
functionally this works out very similar to a home-to-work connection with -L
in that both end up with a LISTENing port at what I call home.
practically, however, the SSH connection this is based on is easier to set up in this direction


  • Similarly, I've used
ssh -R localhost:2222:localhost:22 ssh.home.example.com
so that once home, SSH to localhost port 2222 is actually the SSH server at work (which has SSH open to the work subnet but not to the world)
I'd run this ssh in tmux to
have that SSH and tunnel connection live longer (see notes below)
and stay connected without me having to leave a graphical terminal open with an shell to my home server
...and yes, I'm betting on that connection not dropping on my commute home. There are better ways to deal with that.



Syntax and some security notes

The typical syntax is

listenPort:toHost:toPort

The full form is

listenIP:listenPort:toHost:toPort

and the first was a shorthand for

0.0.0.0:listenPort:toHost:toPort

i.e. to listen on all interfaces.


If you're the only user on that SSH host, then (save for similar trickery) you are the only one that can connect to its localhost, and security-wise it can be preferable to make the tunnel listen on localhost so that only you can connect to that tunnel.

localhost:listenPort:toHost:toPort

(More recently, you can also listen and connect to a named socket, by its path, which is similarly host-only, but remember there is nothing to shield other users on that host from connecting.)


In other cases, you may specifically want e.g. a coworker can use the same tunnel.

Even then, it may be worth noting that all interfaces could include thigns like VPNs, so to keep thinking about what you bind to.


The fact that the tunneled connection does not appear as a separate connection between the hosts is sometimes convenient and more secure, and sometimes convenient and less secure, basically depending on what exactly you do with it.

The convenience often comes from the fact that each host's firewall can be closed to everything but SSH, and this will still work.

This makes firewalling simpler, means you don't need to bother network admins (which they will probably not want to for good security reasons), you won't need exceptions, won't be able to have forgotten exceptions.

However, keep in mind that if you do it wrong enough (listening port is on a public IP), you might unintentionally create a bit of a backdoor.


There are also some practical footnotes, though, like that you'd have to keep the SSH connection open, which by default implies a shell on the other host. You can work around that, though, see notes below.


Limitations to use

  • while the data over the tunnel is encrypted, the extra connection is not
this doesn't matter too much if it's a connection to localhost, but can matter if not.
  • encryption adds a bit of latency, and isn't very high-bandwidth
  • Forwards a single fixed port at at a time.
You can do multiple, but it's certainly not as flexible or user-friendly as VPN, and other generic tunneling (...once you've set those up, that is)
  • only one of these unsecured connections per port(verify)
  • You need to keep the SSH connection open, so need to keep the shell open to keep the tunnel open - or use a way around that (see below)
  • tunneled connections drop when SSH connection drops, for any reason, and don't get re-established unless you've set up something to do that
In some situations this can be prohibitively annoying/fragile
  • you probably can't listen to ports under 1024 (unless you're root)
...which is intentional, and usually a good thing


As such, it's most useful for quick, one-time, temporary use.

Practicalities to the open SSH connection

Mostly "Keeping the connection going" and "Ensuring nothing can get executed at the remote end"


Avoiding having a shell open on it

If you typed in a SSH command just to set up a tunnel, the terminal that contains that SSH command now needs to stay open and visible.


Depending on how and where, that terminal might be found by other people, which may be a security issue for you.

You can hide the ssh command in the backgrounds somewhere (see e.g. screen/tmux).

Ideally, even if that terminal is found and taken control of (admin has power to take over terminals), there is nothing they can do on the other side.


The last isn't hard to do in SSH in that it only defaults to run a shell - if if is running, say,
watch date
instead of a shell, then a Ctrl-C will drop the connection, not drop to a remote shell.


Note that the direction of the SSH connection also relates to the potential risk of someone finding its terminal.


There are a few practical footnotes.

For one, if the connection is one-time and required a person to type in a pass-phrase, then it is enough for the client to ask for that command just this time, because only that one person can make a next connection.


If however the hosts connects automatically, you now need the server end to ensure that command is the only thing that can ever be run.

It turns out this is possible, by tying a command to a specific authorized keys, which may be a nice way of doing a more permanent tunnel anyway, so see SSH_jails#via_authorized_keys)

You could look at SSH jails in general.

Fewer disconnects

You should assume that firewalls and modems will drop idle connections.

For tunnels this is unhandy, as the extra connection will also need to be re-established, so it helps to do your best to never be idle.


The above example of
watch date
is one way to do that.

A more structural fix is configuring ssh/sshd's keepalive, which ensures it occasionally sends a do-nothing packet.

You can configure either or both sides to do that:

For the client-side tweak, look for ServerAliveInterval.
for the server-side configuration, look for ClientAliveInterval


While fewer is handier, you should accept that disconnects will sometimes happen, and you care about...

Automatic re-establishing when disconnects happen anyway

There may be various reasons for the SSH connection to break anyway - and you often want it to reconnect without assistance.


On linux, OSX

Look at autossh, (and/)or abuse your service manager's features.


You'll likely also want a keypair, probably both:

a passphraseless one so you won't need human interaction at reconnection time
and one specific for only this tunnel-supporting connection, because you can configure the server to always run a do-nothing command for a specific key (see also ssh jail).


If you want a tunnel at bootup

Keep in mind that modern service management (systemd, upstart, etc) can watch and respawn things, meaning you don't even really need autossh, but it may be a little easier to still use it

Otherwise you probably want to look at autossh (or perhaps its inspiration, rstunnel).


On windows

Look at things like tunnelier.

Or perhaps ssh / autossh via cygwin.


Autossh notes

Autossh can be seen as a command that keeps re-executing ssh when it needs to.


The simplest autossh command is

autossh -M 0 user@example.com

Notes:

  • -M (monitoring) is a required argument. When you want no monitoring, use -M 0
  • -f tells autossh to sit in the background (forks to init?)
can be useful if you put this in startup scripts, rather than a service
  • options not understood are passed through to ssh, so you can add any of your usual options, say,
-L 3306:localhost:3306 
-o "ServerAliveInterval 60″ -o "ServerAliveCountMax 3″ 


See also:


autossh imitation

If you can't install autossh, then a quick-and-dirty imitation of autossh could be based off commands / script like:

while true
do
  ssh user@hostname  # plus whatever further options you need
  sleep 5            # possibly longer if the server has denyhosts/fail2ban
done


Options you may want on a tunnel

Avoid the idle-disconnect problem:

-o "ServerAliveInterval 60″
-o "ServerAliveCountMax 3″ 


By default, a tunnel failing to establish won't prevent a SSH connection from being made. But if the only point of this connection is that tunnel, then you probably do want it to fail if a tunnel fails:

-o "ExitOnForwardFailure yes"


Use a specific keyfile, rather than relying on things implied by account:

-i SSH_KEY_FILE_PATH

Fail if the login isn't passwordless (that is, if you get a password question, don't hang waiting for timeout - useful for background jobs):

-o BatchMode=yes

X11 forwarding

SSH clients such as the linux one can forward X windowing, so that you can get remote X clients to display on your SSH client side (...yeah, the X terminology makes that sentence a little confusing).

Basically, from another *nix host you can do: (or from windows, e.g. with putty and Xming)

ssh -X otherhost.com

roughly amounts to:

set up a SSH tunnel
setting the DISPLAY variable in the shell to point to that tunnel
setting up X authentication for the connection


Now, in that shell, you can run any X client, and it'll come to you.

The quickest test of whether it works is often
xclock
or
xeyes
as they're likely to be installed, and lightweight to draw.


If X forwarding was not enabled

For this to work, the ssh server (and client) must have X support, and the server must allow it - which may be off by default for security reasons.

Find the server configuration (probably at /etc/ssh2/sshd_config or /etc/ssh2/sshd2_config) and see if there's a:

AllowX11Forwarding        yes


As an admin, you may like to restrict it to a few users, e.g.

Match User myusername
  X11Forwarding yes
  AllowTcpForwarding yes

Notes:

  • Don't forget to restart sshd.
  • SSH may not allow this for root, and even if you coerce it, this may not be ideal security-wise
...and you often don't want to su, because you'll get an auth error "MIT-MAGIC-COOKIE-1 data did not match"
...so set it up for the user you want the first time




On security and broken programs

Apparently, X clients (=GUI programs) don't always deal with authentication properly, which means they may break specifically when X11 does do authentication properly.(verify)

This seems to be the reason that in addition to
ssh -X
, which adheres to X11 SECURITY extensions, there is also
ssh -Y
(and its configuration counterpart,
ForwardX11Trusted
, which is basically the overly trusting version of -X.


More programs work with -Y, but -Y also means clients are allowed to do more potentially bad things, so it's good habit to start with -X and move to -Y only when necessary.

If you don't trust the remote host, don't use -Y. Or, frankly, any X forwarding at all.


See also X_notes#X_Authentication



Related errors

channel 2: open failed: administratively prohibited: open failed

Typically means AllowTCPForwarding is not enabled in the server's /etc/sshd_config

If that system isn't yours, then the sysadmin may never have enabled it, or may have specifically disabled it.

To sysadmins: you can conditionally enable this, e.g. for specific users only.


Authentication refused: bad ownership or modes for directory /home/someone

...in your logs, and keypairs not working.


The following should fix it (but maybe read up on the details):

chmod go-w ~/
chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

That's a little overzealous,

Pseudo-terminal will not be allocated because stdin is not a terminal

This article/section is a stub — probably a pile of half-sorted notes, is not well-checked so may have incorrect bits. (Feel free to ignore, fix, or tell me)

I mostly run into this when I run ssh from things other than a shell (e.g. ssh/scp from cron, a service, and such), so a (pseudo-)terminal does not apply.


You can either disable or force pty allocation. Which of the two is handiest depends on your case.

It seems the options for ssh are:

  • -T
    no pty allocation
  • -t
    force pty
  • -t -t
    (-tt is the same) force pty even if there is no local tty


I ran into this in a more interesting case, where I was trying to automate going to a firewalled host in two ssh steps by trying another ssh command as the command to the first like:

ssh firsthost ssh secondhost

This basically means the inner ssh doesn't need (or get) a pty at all. In short, I needed:

ssh -t firsthost ssh secondhost


Error opening terminal: unknown

This article/section is a stub — probably a pile of half-sorted notes, is not well-checked so may have incorrect bits. (Feel free to ignore, fix, or tell me)

remote port forwarding failed for listen port

This article/section is a stub — probably a pile of half-sorted notes, is not well-checked so may have incorrect bits. (Feel free to ignore, fix, or tell me)

...plus the actual port number.

Often seems to mean there is something already listening on that port.


Which may be something else, but for me was usually just another copy of my own SSH trickery, or a TIME_WAIT thing.

In my case, stopping the autossh service for a few minutes solved the issue.