sFTP on HTML-Kit Tools w/o Port 21 access on the server domain

  • Advertisement ( why? )
     

    superticker, 8th Nov 2012 9:47 pm

    I'm familiar with the SSH tunneling technique to achieve FTP via secure shell with HTML-Kit Tools as discussed at http://www.htmlkit.com/support/docs/pages/h000156.html

    The problem with this tunneling approach is that it requires a insecure port 21 connection somewhere on the server domain side, and our university is no longer providing such connections. Our university has problems with hackers sniffing their networks, so port 21 connection are simply no longer allowed (even on the SSH server).

    So my question is how does one perform an sFTP connection with HTML-Kit Tools without Port 21 (FTP) access on the server domain side? If there is no possible work around, then when will HTML-Kit Tools intrinsically support an sFTP connection (w/o tunneling)?

    • HTML-Kit Support, 9th Nov 2012 6:12 pm

      On 11/8/2012 9:47 PM, superticker wrote:

      I'm familiar with the SSH tunneling technique to achieve FTP via
      secure shell with HTML-Kit Tools as discussed at
      http://www.htmlkit.com/support/docs/pages/h000156.html

      The problem with this tunneling approach is that it requires a
      insecure port 21 connection somewhere on the server domain side, and
      our university is no longer providing such connections. Our
      university has problems with hackers sniffing their networks, so port
      21 connection are simply no longer allowed (even on the SSH server).

      So my question is how does one perform an sFTP connection with
      HTML-Kit Tools without Port 21 (FTP) access on the server domain
      side? If there is no possible work around, then when will HTML-Kit
      Tools intrinsically support an sFTP connection (w/o tunneling)?

      Hi,

      You don't have to open port 21. Depending on server configuration, you
      may need a private connection within the server but it doesn't need to
      be public. Bind it to 127.0.0.1 and you can even change the port.

      Chami

      • superticker, 26th Dec 2012 9:54 pm

        I tried tunneling again this time using WinSCP. The primary connection to the sFTP server works just fine, but this is the log about tunneling part WinSCP returns:

        Connecting via tunnel interface 127.0.0.1:50000
        Looking up host "127.0.0.1"
        Connecting to 127.0.0.1 port 50000
        [Tunnel] Opening forwarded connection to sftp.iastate.edu:22
        [Tunnel] Forwarded connection refused by server: Administratively prohibited [open failed]
        [Tunnel] Closing connection.
        [Tunnel] Sending special code: 12
        [Tunnel] Sent EOF message
        Server unexpectedly closed network connection
        (EFatal) Server unexpectedly closed network connection.
        Error while tunneling the connection.
        Administratively prohibited (open failed).

        If I'm reading this correctly, the university isn't going to allow tunneling on their sftp.iastate.edu servers. Is this the way you read this? Can you find a port on sftp.iastate.edu that will accept a tunnel connection?

        The university is a big red target for hackers (unfortunately), so I can understand why things are locked down.

        My final question is why doesn't HTML-Kit Tools support sFTP natively so tunneling isn't necessary in the first place? Is this hard to do?

        Other IDEs support sFTP natively, and I have considered switching for this reason. But I would prefer not to have to give up HTML-Kit Tools because I really like the product. But I'm running out of choices here.

        • HTML-Kit Support, 30th Dec 2012 9:45 pm

          On 12/26/2012 9:54 PM, superticker wrote:

          I tried tunneling again this time using WinSCP. The primary
          connection to the sFTP server works just fine, but this is the log
          about tunneling part WinSCP returns:

          Connecting via tunnel interface 127.0.0.1:50000
          Looking up host "127.0.0.1"
          Connecting to 127.0.0.1 port 50000
          [Tunnel] Opening forwarded connection to sftp.iastate.edu:22
          [Tunnel] Forwarded connection refused by server: Administratively
          prohibited [open failed]
          [Tunnel] Closing connection.
          [Tunnel] Sending special code: 12
          [Tunnel] Sent EOF message
          Server unexpectedly closed network connection
          (EFatal) Server unexpectedly closed network connection.
          Error while tunneling the connection.
          Administratively prohibited (open failed).

          If I'm reading this correctly, the university isn't going to allow
          tunneling on their sftp.iastate.edu servers. Is this the way you
          read this? Can you find a port on sftp.iastate.edu that will accept a
          tunnel connection?

          The university is a big red target for hackers (unfortunately), so I
          can understand why things are locked down.

          I can understand that as well but tunneling doesn't have to expose
          anything outside the server.

          My final question is why doesn't HTML-Kit Tools support sFTP natively
          so tunneling isn't necessary in the first place? Is this hard to do?

          In addition to licensing issues/costs, SFTP complicates software
          distribution. I want to support SFTP but most likely to happen through a
          separate plugin so that HTML-Kit itself wouldn't be restricted.

          Other IDEs support sFTP natively, and I have considered switching
          for this reason. But I would prefer not to have to give up HTML-Kit
          Tools because I really like the product. But I'm running out of
          choices here.

          I'm not sure if very many dedicated HTML editors support SFTP but if a
          dedicated FTP client like FileZilla won't work for you, this page may
          help with testing other editors:

          http://en.wikipedia.org/wiki/Comparison_of_HTML_editors

          Chami