[vox-tech] Odd ncftp bug

[Ken Bloom]

--UoPmpPX/dBe4BELn
Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


On 2003.09.16 11:35, p@dirac.org wrote:
> On Tue 16 Sep 03, 11:21 AM, Bill Kendrick <nbs@sonic.net> said:
> >
> > I'm noticing an apparent bug in NcFTP (3.1.3; Mar 27, 2002)
> >
> > This works:
> >
> >   $ ftp ftp.server.com
> >   Name: USERNAME
> >   331 User USERNAME okay, need password.
> >   Password: PASSWORD
> >   230 Logged in
> >
> > And this works:
> >
> >   $ ncftp ftp://USERNAME:@ftp.server.com
> >   Logging in...
> >   Password requested by ftp.server.com for user "USERNAME".
> >
> >     User USERNASME okay, need password.
> >
> >   Password: PASSWORD
> >
> >   Logged in.
> >
> >
> > However, in SOME cases, the following does NOT work:
> >
> >   $ ncftp ftp://USERNAME:PASSWORD@ftp.server.com
> >   Logging in...
> >   Could not open host ftp.server.com: username and/or password was
> not accepted
> >
> >
> > Whatintheheck!?  This works for most of the other accounts I've
> tried
> > (I'm writing a script to pull stuff off of various FTP accounts, en
> masse;
> > specifically, my variation is:  "ncftpget -R ftp://USER:PASS@host")
> >
> >
> > The shell is GNU bash 2.05b.0(1)
> > The FTP server is NcFTPd (can't tell which version).
> >
> >
> > Many of the passwords in question include "?", "!", "=3D" and/or "+"
> > characters.  However, this doesn't seem to be an issue, since I
> don't
> > see any pattern where these characters DON'T work, versus when they
> DO.
> >
> > I'm quoting them in the shell, too:
> >
> >   ncftpget -R ftp://USER:"PASSWORD"@ftp.server.com
> >
> >
> > *boggle*
> >
> >
> > Besides changing the passwords to something that ncftpget CAN send
> > properly, is there anything else I can look into!?
>=20
> sure.  this is off the top of my head:
>=20
> 1. http://bugs.debian.org
> 2. http://www.ncftp.com
> 3. http://google.com
> 4. http://www.google.com/advanced_group_search?hl=3Den
> 5. ncftp> debug1
>    ncftp> open (whatever)
> 6. strace -o LOG ncftpget -R ftp://USER:"PASSWORD"@ftp.server.com
> 7. ltrace -o LOG ncftpget -R ftp://USER:"PASSWORD"@ftp.server.com

I see that it's been solved (I tried to send this message earlier only =20
to find out that I hadn't updated my exim configuration to relay to the =20
right host when I arrived in Davis)

Another thing to always check with shells is:

echo ftp://USER:"PASSWORD"@ftp.server.com

just to make sure that the shell is escaping the way you expected.

--
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.
My key was last signed 6/10/2003. If you use GPG, *please* see me about
signing the key. ***** My computer can't give you viruses by email. ***

--UoPmpPX/dBe4BELn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/Z2a6lHapveKyytERApWUAJ9Uey99Y4i7NsFe4ceqEo+29aR1aACfSyqO
mGjmzImoIBXhENHf8QpqjQc=
=mb4Y
-----END PGP SIGNATURE-----

--UoPmpPX/dBe4BELn--