![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2 |
|
Created:
|
19/Apr/13 4:03 PM
|
|
Description:
|
EC2 keypair fingerprints are generated in two different ways. Currently the EC2 plugin only recognizes keypairs generated via AWS. No imported keypairs are allowed.
If AWS generates the keypair, the following command can generate the fingerprint resulting from the private key being hashed:
openssl rsa -in privatekey.pem -outform DER -pubout | openssl sha1 -c
If you generate a public key from the private using ssh-keygen (ssh-keygen -y -f privatekey.pem) and then upload the public key, the fingerprint is calculated off the public key instead of the private key.
You generate the same public key fingerprint that amazon gets via:
openssl rsa -in privatekey.pem -outform DER -pubout | openssl md5 -c
If I put in the ec2 plugin a private key that I generated and then uploaded the public key, the ec2 plugin cannot find the proper resulting fingerprint from the public key.
Could the plugin be updated to either allow entering a public key and private key or have it generate a public key fingerprint as well as the private key fingerprint and check for either?
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Joseph Lawson
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
