![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
stephenconnolly
|
|
Components:
|
ssh-credentials-plugin |
|
Created:
|
26/Jan/15 11:05 AM
|
|
Description:
|
The plugin now supports SSH login using publickey authentication.
In our build network, we sign our SSH server (aka host) public keys and user public keys from an (SSH) CA.
This allows
1. accepting (signed) server-certificates without user interaction (accepting server public key fingerprint)
2. password-less login of users to servers (without need to copy the public key to the server).
This work perfectly using ssh from jenkins master host.
When using the Jenkins SSH Credentials Plugin:
- The first part either
- works or
- the plugin always accepts unknown server public keys.
- The second part does not work:
- When configuring public key authentication, it tries publickey authentication, but when this fails it does not try publickey with certificate authentication.
Note
http://www.jcraft.com/jsch/ does not list support for [email protected] (signed publickey with certificate) host key types.
|
|
Project:
|
Jenkins
|
|
Labels:
|
ssh
ssh_exchange_identification
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tom Ghyselinck
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
