I exported the key as OpenSSH. I tried generating a new key using rsa 2048 instead of 1024 and I get the same error. I see the fingerprint two places. In the output like this: - >> creating keyPair region(us-east-1) group(mygroup) - << created keyPair([region=us-east-1, keyName=jclouds#mygroup#737, fingerprin t=46:bf:10:b6:4b:5d:28:f2:dc:b6:28:f4:02:e4:57:e6, sha1OfPrivateKey=59:4d:90:5e: cb:65:50:b4:59:5f:14:25:b8:bb:96:6f:08:74:09:f2, keyMaterial?=true])
And in the Amazon GUI it shows up with a matching name and fingerprint under key pairs. So I guess when I try to login, using my id_rsa key (as the provided source does) it doesn't work because it created a new pair. On Tue, Jul 23, 2013 at 2:45 PM, Andrew Phillips <[email protected]> wrote: > Running the jar output gives me: >> http://pastie.org/private/**ofodl73bn46tqxkdsopow#<http://pastie.org/private/ofodl73bn46tqxkdsopow#> >> > > Thanks for that. Do you remember whether you exported your private key as > an OpenSSH or ssh.com key? Or did you take the PPK file created by PuTTY > and rename it? > > Are you able to try to create a different keypair using ssh-keygen, e.g. > on a virtual machine, and try with that? > > I shouldn't give the impression that I'm in any way certain that it *is* > the key, but I'd like to at least try to rule that one out as a possible > cause ;-) > > Could you also check whether the fingerprint for the private key shown in > the logs > > fingerprint=a9:82:e4:61:78:4d:**e0:ff:06:c0:20:4d:da:84:6e:83, > sha1OfPrivateKey=e4:7e:ad:ee:**92:04:5d:70:d8:a5:01:ff:f4:b5:** > ea:76:fc:7c:ff:d5 > > matches the fingerprint of the private key you think should be used? Also, > is there any other key (locally or in the EC2 console) that has the > fingerprint > > rsa[fingerprint(e3:b8:ad:91:**57:75:f1:5d:6f:14:ab:06:15:46:** > 8d:fa),sha1(8b:d0:68:78:0a:ea:**d4:1f:f8:e0:5d:0f:32:35:d3:9f:** > d5:6b:fb:06) > > which is what appears to be being used during the login attempt? > > Regards > > ap >
