Provide method to create PKCS12 with encrypted Private Key within a script

未关闭
#1,288 3 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@dopey 已经在做这个了。

开始于 2024年10月8日。

评估

这个 Issue 还没有评估数据。

描述

enhancement needs triage

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

The CLI's step certificate p12 allows for creation of a PKCS12 file using a Certificate and Key pair (e.g. from step certificate create). The current command accepts a --password-file to specify the password to be used to encrypt the created PKCS12 file but there is no equivalent flag to provide the password needed to decrypt (and subsequently encrypt within the PKCS12 file) the Private Key.

Instead, the step certificate p12 command relies upon a TTY input to specify the Private Key password.

Why is this needed?

In an effort to allow better automation via scripts, e.g. in Docker containers, it would be preferable to allow the Private Key password to be provided without TTY input (this also cannot be simulated using Docker's tty: true or bash heredoc piping - the former simply stops the container and requires input that can't be provided, the latter complains that no TTY is available to request the password input).

主要语言
Go
星标
4.3k
派生
320
平均合并
2 天 3 小时
30 天内合并 PR
11

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

smallstep/cli 的其他 Issue

查看 smallstep/cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。