search

digitie / transmission-remote-dotnet

Automatically exported from code.google.com/p/transmission-remote-dotnet
GNU General Public License v3.0
1 stars 0 forks source link

Plink should use -l -t options #240

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The existing Plink (and ssh) support is a nice start.  But you really need to 
start plink with "-l <username> -pw <password> -t" options.

The <username> and <password> should come from the in-memory cache for the 
current transmission session.

The -t option forces the server to allocate a pseudoterminal, so that the 
session can be interactive.

Original issue reported on code.google.com by reardo...@gmail.com on 19 Mar 2010 at 11:15

GoogleCodeExporter commented 8 years ago 
Read SSH wiki page:
http://code.google.com/p/transmission-remote-dotnet/wiki/SSH
"(2) Then you need to setup a session from inside the normal putty.exe client 
(also 
at link above). The session name should be the same as the hostname 
transmission-
remote-dotnet is connecting to. It's optional of course, but you'll probably 
want to 
setup key authentication so you don't have to type a user and pass each time."

Original comment by elso.and...@gmail.com on 21 Mar 2010 at 12:22

GoogleCodeExporter commented 8 years ago 
But the problem remains: you are not using the "-t" option.  This means that a 
pseudoterminal (pty) is not allocated and thus commandline interactions with 
are 
broken.  Eg, I cannot use an interactive script on the remote host.

Original comment by reardo...@gmail.com on 12 May 2010 at 3:10

GoogleCodeExporter commented 8 years ago 
The "-t" option is added by r610. But you should the the username in putty 
settings.

Original comment by elso.and...@gmail.com on 13 May 2010 at 11:31

GoogleCodeExporter commented 8 years ago

Original comment by elso.and...@gmail.com on 14 Jun 2010 at 1:17