Source/build provenance for Windows ssh-keygen.exe 9.5.6.4
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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:
- An official package/build reference identifying these exact bytes, ideally by digest or a verifiable official artifact.
- The corresponding source commit/tag and any relevant Windows servicing patches.
- 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.
- 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時間
- マージ済み PR(30日)
- 7
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
PowerShell/Win32-OpenSSH のほかの issue
-
0 - Backlog Issue-Enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
PowerShell/Win32-OpenSSH#2482 · リアクション 1 件 ·
-
Area-ssh-agent Issue-Upstream Parity
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
PowerShell/Win32-OpenSSH#2458 · コメント 1 件 · リアクション 1 件 ·
-
ssh -t exec path concatenates the command unquoted — GNU-style -c shells lose all but the first word対応中かも @caomengxuan666 が 24 日前に担当しました。 オープン
難易度 3/5 1〜2日 初心者へのやさしさ 62/100
PowerShell/Win32-OpenSSH#2478 · リアクション 2 件 ·
-
Investigate
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
PowerShell/Win32-OpenSSH#2476 · コメント 1 件 · リアクション 1 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
PowerShell/Win32-OpenSSH#2472 · コメント 1 件 · リアクション 1 件 ·
PowerShell/Win32-OpenSSH の issue をすべて見る
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
facebookexperimental/hermit#344 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
CTSRD-CHERI/cheribsd#2769 ·
メンテナーはふだん 2 日以内に返信
-
memory_map: reading a zombie's /proc/pid/maps returns ESRCH on Linux 6.16, failing the maps testオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
-
bug high-priority
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
dividebysandwich/rust-dos#1210 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 2 日以内に返信