I got a solution to the ssh key authentication variant of the problem over on the maves users list (still dont know why the password variant requires keyboard interactive password authentication)
The answer was ... "I guess that Maven uses OpenSSH to open secure connections. Putty Keys are not compatible with OpenSSH. You have to export your Putty key in OpenSSH format and use that file for Maven. AFAIR you can do it in pageant or in puttygen." I used puttygen to load my old key, then used the conversion menu to create an open ssh version. the RC1 artifacts are now being uploaded to http://people.apache.org/~kelvingoodson/sca-java/2.0-M5/RC1/ I'll call a vote as soon as I have everything in place Kelvin. I'll add this to the documentation Kelvin. On Sat, May 29, 2010 at 12:25 PM, kelvin goodson <[email protected]> wrote: > Thanks ant, but it's the p.a.o authentication for logging in to copy > the artifacts thats failing. I tried your suggestion with both > configurations of the settings .xml file (see below) but as I guessed, > it didn't affect the p.a.o authentication > > > <server> > <id>me.people</id> > <username>kelvingoodson</username> > <privateKey>c:\Dev\sshKeyForPAO.ppk</privateKey> > <passphrase>**deleted**</passphrase> > <directoryPermissions>775</directoryPermissions> > <filePermissions>664</filePermissions> > </server> > <server> > <id>me.people2</id> > <username>kelvingoodson</username> > <password>**deleted*</password> > <directoryPermissions>775</directoryPermissions> > <filePermissions>664</filePermissions> > </server> > > On Sat, May 29, 2010 at 12:01 PM, ant elder <[email protected]> wrote: >> Can you try leaving out the -Dgpg.passphrase= part and it should then >> prompt you _once_ for your pass phrase and then reuse that for each >> module without asking again. >> >> ...ant >> >> On Sat, May 29, 2010 at 11:48 AM, kelvin goodson <[email protected]> >> wrote: >>> I've never been able to get the combination of ssh authentication key, >>> with the corresponding pasphrase in the maven settings.xml file and >>> the default code signing key and its passphrase to the point where I >>> can set off a deploy and walk away from it. When I was doing sdo >>> releases I sat there with my p.a.o login password in my paste buffer >>> and pasted the password for every login request caused by ab artifact >>> being scp-ed up. >>> >>> Now that I'm trying to deploy the sca modules that isnt practical so I >>> need to get it right. Can anyone help me please. >>> >>> Here's the relevant stanza in my settings.xml >>> >>> <server> >>> <id>me.people</id> >>> <username>kelvingoodson</username> >>> <privateKey>c:\Dev\sshKeyForPAO.ppk</privateKey> >>> <passphrase>***deleted***</passphrase> >>> <directoryPermissions>775</directoryPermissions> >>> <filePermissions>664</filePermissions> >>> </server> >>> >>> and heres the command I'm running >>> >>> mvn >>> -DaltDeploymentRepository=me.people::default::scp://people.apache.org/hom/public_html/sca-java/2.0-M5/RC1/maven >>> verify gpg:sign install:install deploy:deploy >>> -Dgpg.passphrase=***deleted*** >>> >>> >>> I have in my env ... >>> GNUPGHOME=c:\Dev\gpg\conf >>> >>> and the result of gpg --list-keys is >>> >>> C:\Releasing\2.xm5\tags\sca-java-2.0-M5\modules>gpg --list-keys >>> c:/Dev/gpg/conf\pubring.gpg >>> --------------------------- >>> pub 2048R/71A5225A 2010-05-27 >>> uid Kelvin Goodson (Code Signing Key 2) >>> <[email protected]> >>> sub 2048R/3F48BF74 2010-05-27 >>> >>> >>> when executing the command I see >>> >>> [ERROR] BUILD ERROR >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Error deploying artifact: Authentication failed: Cannot >>> connect. Reason: invalid privatekey: c:\Dev\sshKeyForPAO.ppk >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> >>> but this is the key I register with pageant when using putty to ssh to p.a.o >>> >>> Any clues? >>> >>> Kelvin >>> >> >
