sftp failed after secure shell upgrade

[Grace Li]

After secure shell upgraged to 5.30, my sftp process failed. This process is using "CuteFTP 8.0" software, authenticated by user password.

Syslog shows it ended with "subsystem request for sftp". Please help.

Secure_Shell A.05.30.008
HP-UX titan B.11.23

[Steven Schweda]

I know nothing, but if I were trying to debug
something like this, I'd start by using some
less "Cute" SFTP client program, like, say,
"sftp" on the HP-UX system itself, and adding
"-v" (or "-vv", or ...) to the "sftp" command
line.

Does plain "ssh" work on this system (now)?
If possible, I'd try to get SSH working
before moving onto some SSH-based thing like
SFTP.

[Grace Li]

I can scp / ssh login to unix server via less Graphical software, like winSCP, linux. However, this GUI software failed to login. And I have many scripts to transfer report to the UNIX server under this software. That's why I have to get it fixed.

fyi, it is called "GlobalSCAPT - CuteFTP 8.0 Professional". Since the only change is the upgrade on UNIX side, I work on this direction to check the config of ssh.

[Steven Schweda]

> [...] Since the only change is the upgrade
> on UNIX side, I work on this direction to
> check the config of ssh.

Perhaps, but if there's only one client which
has trouble, then I'd tend to worry about
that client. I'd certainly ask its vendor
about it. At the very least, I'd look for a
way to enable/save some "-v"-style diagnostic
messages from the thing. "my sftp process
failed" is not a very detailed description of
anything by itself.

http://www.cuteftp.com/

[Steven Schweda]

> [...] authenticated by user password.

You're sure that the script is using the
right password? (Of course, one might wonder
if a script using a password is a good idea.
The whole public-key authentication structure
was intended to obviate that sort of security
hole.)

> I can scp / ssh login to unix server via
> less Graphical software, [...]

As the same user which the script uses?
(Using the same password?)

[Tingli]

You can try other sftp software to see whether they work or not.

[Grace Li]

1) password and id is working.
2) because this is gui software, there is loging but it can not be tuned. here is the error log.

Can't connect to "server_name":22. SFTP21 error = #0.

3) check with the software (cuteftp) already, they claim the firewall and config of secure shell on the server side. see below.
/* ---------------------- */
CAUSE
This error is the result of a timeout of an SFTP operation. The first line of error text is irrelevant and should be disregarded. There are two known possible causes for this error:

This problem may be caused by a misconfigured firewall

[Steven E. Protter]

Shalom,

This happens from time to time.

Secure Shell is released with new security features, or flaws fixed and suddenly the client does not work.

You can back out the Secure Shell release or look for an update from the CuteFTP people. If this is being maintained they probably will provide a fix, though you may need to provide them data.

SEP

[Grace Li]

thanks. if i do a swremove, do i need to restart ssh?

[Tingli]

I am not sure whether there is an encryption cipher policy in cuteFTP. If there is, can you move the first one "AES (SSH-2 only)" down and see how it works.