Source/build provenance for Windows ssh-keygen.exe 9.5.6.4

未关闭
#2,490 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c

调研方向

Start by checking the cited Windows source commit and the linked code paths in ssh-keygen.c, authfile.c, and contrib/win32/win32compat/. The issue asks maintainers to identify an official artifact matching the binary’s digest and map it to source and servicing changes, including file security descriptors and the public-file close/reopen path. Done means providing public provenance and applicable source or patch references; the issue does not identify how to obtain that mapping.

由索引模型根据 Issue 内容生成。

描述

Summary of the new feature / enhancement

To the Microsoft Windows OpenSSH maintainers,

Could you help identify publicly available provenance for the exact binary below? Signature/catalog verification and official package/build identification have not been performed. The observed path and version are not being treated as evidence of a particular package.

Field Observed value
SHA-256 c9dc170cd161db87e75eb6cf282f1325005b9e35628b9a36cb19883a8be1a34f
Size 861184 bytes
Architecture AMD64
FileVersion 9.5.6.4
ProductVersion OpenSSH_9.5p2 for Windows
PDB identifier c76e9268-43e2-4fde-b085-6b556b704a14; age 1; ssh-keygen.pdb
Observed path C:\Windows\System32\OpenSSH\ssh-keygen.exe

If available, could you provide:

  1. An official package/build reference identifying these exact bytes, ideally by digest or a verifiable official artifact.
  2. The corresponding source commit/tag and any relevant Windows servicing patches.
  3. References to the Windows code paths creating the private and public outputs during ordinary Ed25519 key-pair generation with an explicit filename and empty passphrase.
  4. Relevant differences from public reference 59aba65cf2e2f423c09d12ad825c3b32a11f408f, particularly the initial security descriptors (owner/DACL) and the public-file close/reopen path described in the attached technical note.

Only information that is available and publicly shareable is requested. We do not assume reproducible builds or availability of all internal build details. If this tracker is not the appropriate route for a Windows-serviced build, an official documentary route would be helpful.

This is a provenance question, not a request for a general security attestation or a workaround. The public reference examined does not meet our strict user-only DACL requirement; we have not established that it corresponds to this binary. Establishing provenance would not itself establish DACL compliance or authorize execution or a change of requirements.

Proposed technical implementation details (optional)

Minimal technical note — proposed public attachment

Field Observed value
SHA-256 c9dc170cd161db87e75eb6cf282f1325005b9e35628b9a36cb19883a8be1a34f
Size 861184 bytes
Architecture AMD64
FileVersion 9.5.6.4
ProductVersion OpenSSH_9.5p2 for Windows
PDB identifier c76e9268-43e2-4fde-b085-6b556b704a14; age 1; ssh-keygen.pdb
Observed path C:\Windows\System32\OpenSSH\ssh-keygen.exe

These are static identifiers already collected, not an authenticated package attribution. Signature/catalog and package/build remain NOT VERIFIED. PDB identity is a correlation aid, not proof of provenance. No executable is attached.

Scope: ordinary Ed25519 key-pair generation, explicit output filename, empty passphrase and fixed comment; no host-key, certificate, conversion or hardware-token mode. Local filenames and comment values are intentionally omitted.

Public reference examined: Windows source commit 59aba65cf2e2f423c09d12ad825c3b32a11f408f. Its applicability to the binary above is NOT DEMONSTRATED. These references are questions for source attribution, not claims about the installed binary:

The examined source routes private and public saves through Windows compatibility code. Its initial descriptor includes Administrators/System ACEs in addition to user permissions; the public mode also introduces broader permissions. It therefore does not satisfy a strict user-only DACL contract. The public fdopen path closes a handle and reopens by pathname. Please identify any applicable servicing differences, including initial descriptors and that reopen path.

An exact source/build mapping is still needed before attributing these observations to the identified binary. No claim of vulnerability, effective access on a machine, or permission to execute is made.

主要语言
没有语言数据
星标
8.4k
派生
824
平均合并
1 天 14 小时
30 天内合并 PR
7

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

PowerShell/Win32-OpenSSH 的其他 Issue

查看 PowerShell/Win32-OpenSSH 的全部 Issue

相似的 Issue

更多 Operating Systems Issue

把新 issue 发到你的邮箱

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