Pack Install Doesn't Honor System user, running as root
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
If you attempt to perform a pack install from a git repo it uses root ssh keys.
From docs:
For SSH (URLs starting with git@) auth you have to create a deploy key, and require the system user running the command (stanley or root, depending on your configuration) to have a private key. Deploy keys are more secure than personal access tokens and can be configured on the per-repo basis.
However since we clone from python action and python action is shelled out as root and not system user this action will always use the root keys.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing pack installation into the Python action that performs the git clone, then inspect how the command's user and SSH environment are selected. Reproduce an SSH-based install while configured for the system user and confirm that it uses that user's key rather than root's; the issue provides no file or test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100