So, here a good one for you.
One of our venders changed out their sFTP server swearing that there
were NO/ZERO changes and there is nothing we need to do. Just an FYI
notice.
Ha! There were two issues:
1. We needed to reset the RSA key for their new server in our
known_hosts file
2. The new sFTP server was throwing an "error" message upon connection
that caused our sFTP routine to fail.
The "error" message was:
Warning: Only authorized users are permitted to connect to this server.
Any unauthorized attempts will be logged and you will be in deep poop.
Once we captured this "error" message by piping std-err to a file (...
2>check_sftp_sterr.txt ) our routine started working fine.
Go figure.
Regards,
Jerry
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.