Thanks Tom. I have tried specifying first SSH2, and then SSH1. Interestingly I get the same result.
Though I have tried turning on the debug mode, I have not gotten any >> different results (though I'm not so sure how to USE the debug mode really). >> > > Are you saying nothing is written to STDOUT or STDERR? > Neither > > Try collecting some data about the target host. Run: > > $ telnet host 22 > > and you should see something like: > > Trying 0.0.0.0... > Connected to 0. > Escape character is '^]'. > SSH-2.0-OpenSSH_4.3p2 Debian-9etch2 > > unless they've obscured the banner, this will tell you what version of the > protocol and what software is being used to implement it. That might provide > some clues when tracking down an incompatibility with the SSH module. > Compare that to the hosts that are working OK. > They HAVE obscured their banner. But I have asked for them to get some of this info for me. > > I'd then check rt.cpan.org for bug reports relating to this for the SSH > module. If you determine that the SSH module is failing to login only with a > specific SSH server implementation, then you should file a bug at > rt.cpan.org. > Will look. Thanks. I always forget about rt.cpan.org > > Try coding up a simple test that uses the SSH module to login. That'll take > the SFTP module out of the picture and make it easier to debug. Try it with > both SSH1.pm and SSH2.pm. Try it first with a known working host. will do that next. Bill's suggestions: I tried ssh -v and got the following output: [EMAIL PROTECTED] ~]$ ssh -v XXXX.com OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to XXXX.com [###.###.###.###] port 22. debug1: Connection established. debug1: identity file /home/alexb/.ssh/identity type -1 debug1: identity file /home/alexb/.ssh/id_rsa type -1 debug1: identity file /home/alexb/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5p1 FreeBSD-20061110 debug1: match: OpenSSH_4.5p1 FreeBSD-20061110 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'data-access.sandiegomedia.com' is known and matches the DSA host key. debug1: Found key in /home/alexb/.ssh/known_hosts:4 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/alexb/.ssh/identity debug1: Trying private key: /home/alexb/.ssh/id_rsa debug1: Trying private key: /home/alexb/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive Anyway for me to check for certain from my end if the allow "suppress shell"? Seems like we've got a few supporters for Net::SCP::Expect. So i installed it and tested it out. It worked on this server! I've never used this module before, so I've got a couple quick questions about it: - Is there any reason to worry about my current servers that work with the SFTP module working with this SCP module? - Are there any known "gotchas" with using Net::SCP::Expect? - Simply put: should it work anywhere clients are expecting to use SFTP? I do not have any control over the servers that are being programmed for our servers to connect to. So I need to program I a way that can handle most/all cases. Right now we offer local/manual download, HTTP, FTP, & SFTP. Thanks again for all of the help. --Alex _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
