I would go so far as to say thaty ou should NEVER automate the copying of your keys.

That's about on par with automating the installation of sshd on the remote machine everytime you wanted to connect.

That said, if you can can get your ssh keys set up so that your normal, commandline ssh client can connect to your romote system, then you should be good to go -- just don't specify a password to $ssh->login($user).

(You might run into passphrase issues ... but I think Net::SSH::Perl can deal with a key agent if you have one running -- I would guess that if you're trying to automate something, you probably want to use passphraseless key's anyway.)

In reply to Re: Re: scp and ssh without passwd by hossman
in thread scp and ssh without passwd by perlknight

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.