`step certificate inspect` should support using StartTLS
维护者通常 1 天内回复
@darkfronza 已经在做这个了。
开始于 2025年9月4日。
评估
这个 Issue 还没有评估数据。
描述
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
It would a nice addition to support inspecting certificates that use explicit TLS (StartTLS negotiates a potential upgrade to TLS from a cleartext connection), which could use a flag like --starttls to indicate the connection uses StartTLS instead of implicit TLS:
step certificate inspect --starttls smtp.example.com:587
Related was an issue that lead to adding a smtps:// scheme prefix implying port 465 (implicit TLS), but SMTPS was commonly associated to implicit TLS equivalent to port 25 (StartTLS), however in 2018 was reassigned via RFC 8314 as the implicit TLS equivalent to the submission port (587 with StartTLS). So I don't know how much value that's providing vs just being explicit with a port number 😅 (there's help output with the smtps:// scheme, but no indication of the associated port)
Why is this needed?
The main benefit is it would not require an alternative tool to acquire a certificate from services only reachable via StartTLS:
openssl s_client -starttls smtp -connect smtp.example.com:587
StartTLS is often found with mail servers (aka explicit TLS via ports 25 and 587 related to SMTP and 110 + 143 for POP3/IMAP), which don't always offer implicit TLS ports (465, 993, 995). It can also be found elsewhere like Postgres databases (although this now offers implicit TLS too).
From what I understand however, supporting StartTLS varies by protocol, so implementing support may not be worth the effort/maintenance burden if it cannot be offloaded via some existing library? OpenSSL documents a -starttls option with a fairly long list of supported protocols.
- 主要语言
- Go
- 星标
- 4.3k
- 派生
- 320
- 平均合并
- 2 天 3 小时
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
smallstep/cli 的其他 Issue
-
bug needs triage
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
enhancement needs triage
难度 4/5 3-5 天 新手友好度 32/100
维护者通常 1 天内回复
-
enhancement needs triage
难度 3/5 1-2 天 新手友好度 57/100
smallstep/cli#1713 · 1 个 reaction ·
维护者通常 1 天内回复
-
enhancement needs triage
难度 4/5 3-5 天 新手友好度 35/100
smallstep/cli#1710 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
[Bug]: `step ca provisioner add --ca-config` requires `--ca-url`/`--root` even for purely local/offline edits可能已有人在做 @vulragrag-star 于 51 天前认领。 未关闭bug needs triage
难度 4/5 3-5 天 新手友好度 20/100
smallstep/cli#1705 · 1 个 reaction ·
维护者通常 1 天内回复
相似的 Issue
-
agent-butler-finding bug
难度 2/5 1-3 小时 新手友好度 82/100
jordansmall/spindrift#6414 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
Icinga/icinga-kubernetes#294 ·
维护者通常 4 天内回复
-
kind/design sig/ui
难度 1/5 1 小时以内 新手友好度 92/100
kubermatic/dashboard#8449 ·
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 62/100
cli/cli#14962 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
model-drift
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复