Menu

#1838 FTP plugin 1.3 : alertnate port problem

open
nobody
None
5
2016-01-27
2016-01-27
No

Hi,

I have problem to choose an alternate port in jedit FTP plugin, I suspect it is version related (this was working before)

My config :
OS : Debian Jessie (8.2)
jEdit version : 5.1.0 (installed from APT)
FTP plugin version : 1.3 (installed from manager)

Step to reproduce :
1 ) 'Plugin'->'FTP'->'Connect sftp'
2 ) In Host put "@IP:port" (ie : 1.2.3.4:10222)
3 ) try to connect

Activity.log (extract) :
11:31:18 [AWT-EventQueue-0] [debug] String: sftp://myuser@192.168.1.4:10222/~/
11:31:18 [jEdit Worker #3] [debug] ConnectionManager: Thread[jEdit Worker #3,6,jEdit Workers]: Connecting to sftp://192.168.1.4:10222
11:31:18 [jEdit Worker #3] [debug] SFtpConnection: info.privateKey=null
11:31:18 [jEdit Worker #3] [message] SftpLogger: Connecting to 192.168.1.4 port 22

-> So i try to connect on '192.168.1.4' port 10222 and I see in activity log sftp still trying to connect on default port (22)

Discussion

  • Alan Ezust

    Alan Ezust - 2016-01-27

    Why are you not supplying a username here? Are you relying on an entry in your .ssh/config file?

     
  • Alan Ezust

    Alan Ezust - 2016-01-27

    Also, the @ sign you entered in the hostname field is not necessary and probably is not helping.

     
  • Infra Option Service

    Why are you not supplying a username here?
    My bad, I supply it and forgot to mention it

    Step to reproduce :
    1 ) 'Plugin'->'FTP'->'Connect sftp'
    2 ) In Host put "192.168.1.4:10222"
    3 ) username put "myuser"
    4) password put "mypassword"
    5 ) try to connect

    Are you relying on an entry in your .ssh/config file?
    No I don't try to use this feature

    When try to connect I see with tcpdump that port 22 is used than port 10222

    tcpdump -n host 192.168.1.4
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
    15:55:43.145075 IP 10.0.1.14.42982 >192.168.1.4.22: Flags [S], seq 425722214, win 29200, options [mss 1460,sackOK,TS val 283178772 ecr 0,nop,wscale 7], length 0

     
  • Infra Option Service

    Are you relying on an entry in your .ssh/config file?

    I confirm this can works as workaround, if i .ssh/config I had

    Host client.test
    hostname 192.168.1.4
    port 10222
    user myuser

    and have configured id_rsa

     

Log in to post a comment.