Re: sftp issue after V7R1 to V7R3 upgrade

solved the issue - until i can generate new keys with partner,
changed sysval QSSLPCL to recognize older versions.
There is no proprietary or personal info to worry about..
Also the -vvv is as verbose as it gets - was failing for the above issue,
generating
a small log with "No route to host as the clue...
Found a previous log where it was working - and "needpriv 0" is normal..
Full log is over 250 lines of detail.

Jim


On Sun, May 27, 2018 at 9:12 PM, Jim Franz <franz9000@xxxxxxxxx> wrote:

I knew TLS levels changed in V7R2.

This is current log failing
SFTP in connecting
OpenSSH_6.9p1, OpenSSL 1.0.2n 7 Dec 2017

debug1: Reading configuration data /QOpenSys/QIBM/ProdData/SC1/
OpenSSH/etc/ssh_config
debug2: ssh_connect: needpriv 0

debug1: Connecting to xx.0.xx.xx [xx.0.xx.xx] port 22.

debug1: connect to address xx.0.xx.xx port 22: No route to host

my clp log has Command ended normally with exit status 255.

The i server has a self singed key created at V7R1 couple years ago.

1. Trying to remember how to turn on a higher level of logging
/QOpenSys/usr/bin/ && sftp -vvv -b currently but this is far less
logging than when I set it up

2. anyone have sftp problems after leaving v7r1, using keys generated
during v7r1 (I tried to ask this several months ago but no clear response).
At this point with partner, not an option to generate new keys till next
week...

Jim