Mercurial > gftp.yaz

--- a/ChangeLog	Tue Sep 14 10:16:52 2004 +0000
+++ b/ChangeLog	Tue Sep 14 10:24:01 2004 +0000
@@ -1,4 +1,6 @@
 2004-9-14 Brian Masney <masneyb@gftp.org>
+	* docs/gftp-faq.sgml - updated SSH section
+
 	* lib/gftp.h lib/bookmark.c lib/local.c lib/rfc2068.c lib/rfc959.c
 	lib/sshv2.c src/gtk/transfer.c src/uicommon/gftpui.c - removed
 	need_userpass from the gftp_request structure. Added need_username and
@@ -2817,7 +2819,7 @@

 	* cvsclean - added this script

-	* *.[ch] - added $Id: ChangeLog,v 1.320 2004/09/14 10:16:52 masneyb Exp $ tags
+	* *.[ch] - added $Id: ChangeLog,v 1.321 2004/09/14 10:24:01 masneyb Exp $ tags

 	* debian/* - updated files from Debian maintainer
--- a/docs/gftp-faq.sgml	Tue Sep 14 10:16:52 2004 +0000
+++ b/docs/gftp-faq.sgml	Tue Sep 14 10:24:01 2004 +0000
@@ -6,7 +6,7 @@
 <book>

 <bookinfo>
-  <date>$Date: 2004/04/15 00:59:23 $</date>
+  <date>$Date: 2004/09/14 10:24:01 $</date>
   <title>gFTP FAQ</title>
   <authorgroup>
     <author>
@@ -336,6 +336,96 @@
 <!-- ***************************************************************** -->

 <chapter>
+<title>SSH Protocol</title>
+
+<sect1>
+<title>gFTP will not log into the remote SSH server when using a non-English
+locale.</title>
+
+<para>
+You will need to download the source code to gFTP and edit the appropriate
+po/&lt;lang&gt;.po file. You will need to make sure the following strings
+are translated exactly as they appear in the SSH client.
+</para>
+
+<itemizedlist>
+<listitem><simpara>Enter passphrase for RSA key</simpara></listitem>
+<listitem><simpara>Enter passphrase for key</simpara></listitem>
+<listitem><simpara>Password</simpara></listitem>
+<listitem><simpara>password</simpara></listitem>
+</itemizedlist>
+
+<para>
+Please upload the changes to the PO file to GNOME's CVS or email me the
+updated PO file. If you email me the updates, please make sure that you
+grab the latest PO file from CVS.
+</para>
+
+</sect1>
+
+<!-- ----------------------------------------------------------------- -->
+
+<sect1>
+<title>I'm having problems getting SSH2 transfers to work. I keep getting the
+error: <emphasis>Error: Message size XXXXXXXX too big from server (only relevant for versions <= 2.0.17)</emphasis>
+</title>
+
+<para>What probably is the problem, sftp-server isn't in your path on the
+remote server. When you try to connect to the remote server, you'll see the
+command gFTP is trying to run, and it'll look something like:</para>
+
+<para><literallayout><literal>ssh -e none -l username hostname "echo -n xsftp ;  sftp-server"</literal></literallayout</para>
+
+<para>Try running this command. If you get a prompt asking:</para>
+
+<para><literallayout>
+<literal>The authenticity of host 'hostname (###.###.###.###)' can't be established.</literal>
+<literal>RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.</literal>
+<literal>Are you sure you want to continue connecting (yes/no)?</literal>
+</literallayout></para>
+
+<para>Tell it yes. gFTP won't even try to answer this question for you at the
+moment. Then, if you get the following output:</para>
+
+<para><literallayout>
+<literal>Enter passphrase for key '/home/brian/.ssh/id_dsa':</literal>
+<literal>xsftp</literal>
+<literal>bash: sftp-server: command not found</literal>
+</literallayout></para>
+
+<para>You'll have to set the path to the sftp-server program. Alternatively
+you could go under FTP->Options->SSH and enable Use sftp subsys. If you enable
+this, then you don't have to know the remote path to your sftp executable.
+But if you enable this, gFTP won't be able to send your password over to
+the ssh client. So if you're not using ssh-agent, then ssh will spawn the
+ssh-askpass program to grab your password.</para>
+
+</sect1>
+
+<!-- ----------------------------------------------------------------- -->
+
+<sect1>
+<title>What is the difference between the SSH and SSH2 protocols? (only relevant for versions <= 2.0.15)</title>
+
+<para>The SSH protocol uses sftp >= 0.7 from
+<ulink url="http://www.xbill.org/sftp">http://www.xbill.org/sftp</ulink>.
+SSH2 uses the native file transfers found in the commercial SSH2 and in later
+versions of OpenSSH. The SSH2 protocol uses the sftp-server executable on
+the remote host and the SSH protocol uses the sftpserv executable.</para>
+
+<para>Note: Due to confusion, the origional SSH protocol was removed in gFTP
+2.0.15. It is not shown in gFTP 2.0.14, but there is a config option called
+enable_old_ssh to enable this protocol.</para>
+
+</sect1>
+
+<!-- ----------------------------------------------------------------- -->
+
+</chapter>
+
+<!-- ***************************************************************** -->
+
+<chapter>
 <title>SSL Issues</title>

 <sect1>
@@ -398,60 +488,6 @@
 <title>Issues for older releases</title>

 <sect1>
-<title>I'm having problems getting SSH2 transfers to work. I keep getting the
-error: <emphasis>Error: Message size XXXXXXXX too big from server (only relevant for versions <= 2.0.17)</emphasis>
-</title>
-
-<para>What probably is the problem, sftp-server isn't in your path on the
-remote server. When you try to connect to the remote server, you'll see the
-command gFTP is trying to run, and it'll look something like:</para>
-
-<para><literallayout><literal>ssh -e none -l username hostname "echo -n xsftp ;  sftp-server"</literal></literallayout</para>
-
-<para>Try running this command. If you get a prompt asking:</para>
-
-<para><literallayout>
-<literal>The authenticity of host 'hostname (###.###.###.###)' can't be established.</literal>
-<literal>RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.</literal>
-<literal>Are you sure you want to continue connecting (yes/no)?</literal>
-</literallayout></para>
-
-<para>Tell it yes. gFTP won't even try to answer this question for you at the
-moment. Then, if you get the following output:</para>
-
-<para><literallayout>
-<literal>Enter passphrase for key '/home/brian/.ssh/id_dsa':</literal>
-<literal>xsftp</literal>
-<literal>bash: sftp-server: command not found</literal>
-</literallayout></para>
-
-<para>You'll have to set the path to the sftp-server program. Alternatively
-you could go under FTP->Options->SSH and enable Use sftp subsys. If you enable
-this, then you don't have to know the remote path to your sftp executable.
-But if you enable this, gFTP won't be able to send your password over to
-the ssh client. So if you're not using ssh-agent, then ssh will spawn the
-ssh-askpass program to grab your password.</para>
-
-</sect1>
-
-<sect1>
-<title>What is the difference between the SSH and SSH2 protocols? (only relevant for versions <= 2.0.15)</title>
-
-<para>The SSH protocol uses sftp >= 0.7 from
-<ulink url="http://www.xbill.org/sftp">http://www.xbill.org/sftp</ulink>.
-SSH2 uses the native file transfers found in the commercial SSH2 and in later
-versions of OpenSSH. The SSH2 protocol uses the sftp-server executable on
-the remote host and the SSH protocol uses the sftpserv executable.</para>
-
-<para>Note: Due to confusion, the origional SSH protocol was removed in gFTP
-2.0.15. It is not shown in gFTP 2.0.14, but there is a config option called
-enable_old_ssh to enable this protocol.</para>
-
-</sect1>
-
-<!-- ----------------------------------------------------------------- -->
-
-<sect1>
 <title>I downloaded a binary off the internet and everytime I run gFTP I get an
 error saying: <emphasis>undefined symbol :__register_frame_info</emphasis></title>