SSH connection does not work for remote users without interactive shell access

[GoogleCodeExporter]

What steps will reproduce the problem?
Trying to connect to a server where a user only has tunnelling access. The 
shell for this user has been set to /bin/false and in the user's 
authorized_keys the key I'm using has been prepended with the options 
'permitopen="127.0.0.1:3306",no-pty'. Manually creating a SSH tunnel using 'ssh 
-N -L 3333:localhost:3306 vm.dev' and connecting to that one works as expected. 
However it seems that Sequel Pro is trying to enter an interactive shell on 
which it fails, even though, as can be seen in the log below, the tunnel is 
established.

What is the expected output? A working connection with the MySQL server
What do you see instead? "The SSH Tunnel has unexpectedly closed."

What version of Sequel Pro are you using? Nightly (r4110) / 1.0.2
What version of OS X are you using? 10.8.4
What version of MySQL are you connecting to on the server? 5.5

Relevant log:
Authenticated to vm.dev ([192.168.242.50]:22).
debug1: Local connections to LOCALHOST:59178 forwarded to remote address 
127.0.0.1:3306
debug1: Local forwarding listening on ::1 port 59178.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 127.0.0.1 port 59178.
debug1: channel 1: new [port listener]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
Write failed: Broken pipe

Original issue reported on code.google.com by ru...@gewooniets.nl on 30 Jul 2013 at 8:10

[GoogleCodeExporter]

Sequel Pro specifies the "-N" option on connect.

Also if you try the ssh command with "-v" you will see that the output will say 
"Entering interactive session." even when "-N" is set.

Your debug log should contain the full command SP used at the top. Try that in 
command line and then either post both full logs here or send them via mail to 
sequelpro@northofthree.com

Original comment by schlabbe...@gmail.com on 1 Aug 2013 at 7:29

• Changed state: WaitingOnUser

[GoogleCodeExporter]

Looks like I was in error. There was a problem with the configuration at the 
server end of it all. Copying the command from the Sequel Pro log quickly 
showed that. Thanks for your help.

Original comment by ru...@gewooniets.nl on 3 Aug 2013 at 5:27

[GoogleCodeExporter]

Ok then. :)

Original comment by schlabbe...@gmail.com on 4 Aug 2013 at 9:01

• Changed state: Invalid