Pulling from private repository with passphrase protected key fails
Metadata
Current evaluation
Snapcraft 8.0.2 with --bind-ssh fails to prompt for a passphrase-protected SSH key during a private Git clone; no fix or maintainer triage is recorded.
Suggested action: needs triage
Reason: The report provides a specific version, flag, private-repository clone, and Git exit code 128, while the current provider code only mounts ~/.ssh and contains no passphrase or SSH-agent handling. However, the issue has no labels, assignee, comments, maintainer response, or complete reproducer, so the expected interactive behavior and root cause remain unconfirmed.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
12
Complexity:
55
Confidence:
75
Actionability:
58
Issue body
When using snapcraft --bind-ssh with a key that is passphrase protected, the passphrase is never asked and snapcraft fails.
logs:
Starting Snapcraft 8.0.2
Logging execution to '~/.local/state/snapcraft/log/snapcraft-20240212-125110.139787.log'
Running on amd64 for amd64
Launching instance...
Creating instance from base instance
Starting instance
Starting Snapcraft 8.0.2
Logging execution to '/tmp/snapcraft.log'
Running on amd64 for amd64
Initializing parts lifecycle
Installing build-packages
Installing build-snaps
Pulling cos-registration-agent
Failed to pull source: command ['git', 'clone', '--recursive', '<email address hidden>:test/test.git', '/root/parts/test/src'] exited with code 128.
Make sure sources are correctly specified.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
12
Complexity:
55
Confidence:
75
Actionability:
58
|
needs triage | Snapcraft 8.0.2 with --bind-ssh fails to prompt for a passphrase-protected SSH key during a private Git clone; no fix or maintainer triage is recorded. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
16
Complexity:
52
Confidence:
76
Actionability:
72
|
needs triage | Snapcraft 8.0.2 with --bind-ssh does not prompt for an encrypted SSH-key passphrase, so private Git pulls fail with clone exit 128; open and untriaged. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
9
Complexity:
71
Confidence:
85
Actionability:
68
|
needs triage | Untriaged Snapcraft 8.0.2 report: private Git pulls with --bind-ssh fail for a passphrase-protected SSH key without prompting for its passphrase. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
40
Quick Win:
20
Staleness:
85
Complexity:
50
Confidence:
50
Support Request:
10
|
needs triage | snapcraft --bind-ssh fails to prompt for passphrase when using passphrase-protected SSH keys to clone private repositories. Untriaged, no maintainer response after 933 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
35
Confidence:
80
Support Request:
10
|
needs triage | Snapcraft fails to prompt for an SSH key passphrase during source pulling, causing git clone to fail. Unaddressed for ~2.4 years with no maintainer labels or comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Snapcraft fails to prompt for SSH key passphrases when pulling from private repositories, causing git clone to fail with exit code 128. Issue is unlabelled, has zero comments, and has been inactive for over two years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Snapcraft fails to prompt for SSH key passphrases when pulling from private repositories. No maintainer response or comments in over two years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#3796
(confidence 84%)
The historical SSH-directory binding implementation is the relevant code path; current providers.prepare_instance still mounts ~/.ssh without handling encrypted keys.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5661 Snapcraft hangs forever if a GitHub repository doesn't exist | snapcraft | open | Snapcraft 8.10.2 hangs during part pulls when Git prompts for credentials; maintainers assigned the fix to craft-parts, where the equivalent issue remains open. |