Perfect suggestion!! In the code I had

$ssh2->auth_password($login{user}, $login{password}) ; $ssh2->auth_ok() ;
and I was assuming that auth_ok was telling me truth. Not so. As you suggested, I put in an explicit error check on the auth_password and now I get:
d:\Desktop>sshtest Authentication failed (username/password) (-18 LIBSSH2_ERROR_PUBLICKEY +_UNRECOGNI ZED) at D:\Desktop\sshtest.pl line 13.
Now I have to figure out what PUBLICKEY_UNRECOGNIZED means. I think it means that it doesn't recognize the servers key and I need to figure out how to get that "accepted" -- I know I've had to do that in my sftp and ssh clients, I didn't think it'd be a problem with this. Is it worth a bug-report on Net::SSH2 that auth_ok doesn't seem to work?

In reply to Re^4: Net:SSH2 channels by BernieC
in thread Net:SSH2 channels by BernieC

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.