jenkinsci / jenkinsci/ssh-credentials-plugin

[JENKINS-52232] Credentials not usable after upgrade to 1.14

Open
#305 18 comments 0 reactions 0 assignees View on GitHub
component:ssh-credentials-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
25
Forks
69
PR merge metrics
No merged PRs in 30d

Description

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.

---
Originally reported by jenkey, imported from: Credentials not usable after upgrade to 1.14


  • status: Reopened
  • priority: Major
  • component(s): ssh-credentials-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 8
  • imported: 20251215-193512

Raw content of original issue

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.