Pulling from private repository with passphrase protected key fails
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and no assignee after 933 days. It reports a legitimate bug where SSH passphrase prompts don't appear when using --bind-ssh with passphrase-protected keys, but requires maintainer assessment to determine if it's still relevant or has been addressed in newer versions.
Impact:
40
Quick Win:
20.0
Staleness:
85
Complexity:
50
Confidence:
50
Support Request:
10
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 |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
40
Quick Win:
20.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
50
Confidence:
80
Support Request:
10
|
needs triage | Snapcraft fails to prompt for SSH key passphrase when pulling from private repositories using --bind-ssh, causing git clone to fail. Unanswered for over 2 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2052928 Pulling from private repository without known_hosts hangs forever | snapcraft (launchpad) | open | SSH pull from private repo hangs when known_hosts is missing; SSH authenticity prompt is hidden by snapcraft progress bar. Untriaged, 935 days old. | |
| #5661 Snapcraft hangs forever if a GitHub repository doesn't exist | snapcraft | open | Snapcraft hangs indefinitely on Pulling when a git source is missing/private because git prompts for credentials. Triaged by maintainers; fix identified (GIT_TERMINAL_PROMPT=0) but must be implemented in craft-parts, not yet done. | |
| #2018456 Lack of support for ssh agent | snapcraft (launchpad) | open | Untriaged issue from 1218 days ago about snapcraft pull --bind-ssh getting stuck during git clone via SSH. No maintainer response or labels. | |
| #2008502 mishandled private git+ssh repo url | snapcraft (launchpad) | open | Snapcraft 7.2.8 treats a git+ssh:// source URL as a local file path when cloning a private Launchpad repo, so git clone fails. No maintainer response in over 3 years; the pip-style scheme is invalid for git, which only accepts ssh:// or user@host:path forms. |