-
Bug
-
Resolution: Unresolved
-
Major
-
None
I have upgraded to ssh-credentials version 1.14 which fixes SECURITY-440 / CVE-2018-1000601.
After upgrading from version 1.13, no job could authenticate to Github, since the credentials was using a "private key file on master".
According to the announcment:
> Existing SSH credentials of these kinds are migrated to "directly entered" SSH credentials.
This seems not to work for me. I do not see `SECURITY-440: Migrating FileOnMasterPrivateKeySource to DirectEntryPrivateKeySource` message in the logs and the "private key" input box of the credentials is just empty.
- is duplicated by
-
JENKINS-55971 SSH Host key matches, Authentication failed, Slaves failed to reconnect
-
- In Review
-
-
JENKINS-54746 Can't connect via SSH on 1.29.1
-
- Closed
-
- is related to
-
JENKINS-54746 Can't connect via SSH on 1.29.1
-
- Closed
-
[JENKINS-52232] Credentials not usable after upgrade to 1.14
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Resolution | Original: Cannot Reproduce [ 5 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Link | New: This issue is duplicated by JENKINS-55971 [ JENKINS-55971 ] |
Link |
New:
This issue is duplicated by |
Assignee | Original: Devin Nusbaum [ dnusbaum ] |
Link |
New:
This issue is related to |