An easy way to set up public key authentication from a Windows machine:
- Generate the public/private key pair in a linux box using ssh-keygen without passphrase. For instance:
$ ssh-keygen -f win_id_rsa
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in win_id_rsa.
Your public key has been saved in win_id_rsa.pub.
The key fingerprint is:
df:25:e9:a5:12:b1:ea:bf:fa:41:23:62:88:cb:4b:1e salva@topo
The key's randomart image is:
+--[ RSA 2048]----+
| |
| |
| . |
| . . o . |
| . . o S = o o |
| . . . . = = = |
| E . + + |
| o o . o |
| o o++. |
+-----------------+
- Copy both the public and the private keys in some private folder in your Windows machine (you can use scp from the command line or WinSCP or FileZilla).
- For every server and every account where you want to log using public key authentication, append the contents of the file with the public key (i.e. win_id_rsa.pub) into the file ~/.ssh/authorized_keys.
- When using Net::SSH::Any, pass the path to the file containing the private key (i.e. win_id_rsa) via key_path.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|