That's why, at the end of my [extremely long] post, I put in the
instructions for how to do it.
On 7/28/06, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> <filePermissions>664</filePermissions>
> </server>
>
> The .ppk file indicated is the same one I was supplying to
> pageant to allow
> my caveman brain to not have to remember the passwords for
> the remote hosts.
Note, that PuTTY's keys have an own format. You must export the key in the
proper format (can be done with the same tool you are creating the PuTTY key
- just can't remember the name).
[snip]
This being what got [snipped]...
2. The key file I produced using puttygen (version 0.58 in my case) is
incompatible with the ssh wagon. This one was nagging me, like when the elk
manages to escape even though you have stalked it for many hours.
I remembered an Export function in puttygen. I started puttygen and
looked for that function. "Export" looked like a promising menu choice. As
did "OpenSSH key" under "Export".
It turns out that if one loads the private key back into puttygen in and
"Exports"->"OpenSSH keyfile" (with a different name of course like
sourceforge-Shell-openssh.ppk), then points the privateKey field to the
NEW keyfile, and supplies the <passphrase> for that new keyfile, it works
flawlessly. It's all a question of format of the putty keyfile. This may
be documented somewhere, but like a lot of the maven documentation, it's
probably in the one place that caveman programmers would never look. Like
near the SOAP calls. :)
My NEW settings.xml has this server def:
<server>
<id>site-id</id>
<username>myusername</username>
<privateKey>c:/putty/sourceforge- Shell-openssh.ppk
</privateKey>
<passphrase>keyfilepassphrase</passphrase>
<directoryPermissions>775</directoryPermissions>
<filePermissions>664</filePermissions>
</server>
I only use that privateKey for doing maven deployments. The other key (in
the putty format) is the one I load into Pageant to allow me to ssh to
remote hosts without unencrypted authentication across the wire.
