Re: Using ssh and scp from QShell and/or PASE? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 11/20/18, 11:04 AM, Kevin Adler wrote:

scp and sftp do not support password or otherwise interactive operation
from QSH or QP2TERM - you must use public-key authentication (it does work
if you call them from SSH).

It didn't work for me even in ssh. Here's an excerpt from the end of the "-vvv" debug info (the names have been changed to protect the innocent) produced by an ssh attempt from a QP2TERM session:

debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred:
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: No such device or address
debug2: readpassphrase: turning 5250 echo off
foo@xxxxxxxxxxx's password: debug2: readpassphrase: turning 5250 echo previous
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
Permission denied, please try again.
debug1: read_passphrase: can't open /dev/tty: No such device or address
debug2: readpassphrase: turning 5250 echo off
foo@xxxxxxxxxxx's password:

--
JHHL

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.