无法指向Jenkins主机上〜/.ssh中的ssh密钥 [英] Unable to point to ssh keys in ~/.ssh on Jenkins host

查看:244
本文介绍了无法指向Jenkins主机上〜/.ssh中的ssh密钥的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经安装了SSH代理插件以使用SSH身份验证提取Git存储库.我想使用位于系统文件中的SSH密钥(来自Jenkins master ~/.ssh选项).这是从官方插件页面上截取的屏幕截图:

很遗憾,我没有看到此选项.我只能选择直接输入".请查看我的屏幕截图.

我配置错了吗?

解决方案

这是最近发布的更改,在安全公告440中进行了解释:

SSH凭据插件不再支持Jenkins主文件系统上文件中的SSH凭据,既不支持用户指定的文件路径,也不支持〜/.ssh.这些类型的现有SSH凭据将迁移到直接输入"的SSH凭据.

I've installed SSH Agent Plugin to pull Git repository using SSH authentication. I'd like to use SSH keys located in system file (from the Jenkins master ~/.ssh option). It's screenshot taken from official plugin's page:

Unfortunately I don't see this option. I can select only "Enter directly". Please check out my screenshot.

Did I configure something wrong?

解决方案

This is a reletively recent change, explained in security advisory 440 : https://jenkins.io/security/advisory/2018-06-25/

SECURITY-440 / CVE-2018-1000601 SSH Credentials Plugin allowed the creation of SSH credentials with keys "From a file on Jenkins master". Credentials Binding Plugin 1.13 and newer allows binding SSH credentials to environment variables. In combination, these two features allow users with the permission to configure a job to read arbitrary files on the Jenkins master by creating an SSH credential referencing an arbitrary file on the Jenkins master, and binding it to an environment variable in a job.

SSH Credentials Plugin no longer supports SSH credentials from files on the Jenkins master file system, neither user-specified file paths nor ~/.ssh. Existing SSH credentials of these kinds are migrated to "directly entered" SSH credentials.

这篇关于无法指向Jenkins主机上〜/.ssh中的ssh密钥的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆