oxidecomputer / oxidecomputer/helios-engvm
seed ssh key from .pub key?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 64
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
On several systems where I do not have inbound ssh enabled, I do not have an authorized_keys files. Is it possible to instead use the id_xxx.pub instead to seed this rather than having the user creating a temporary set of allowed keys?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files or tests; start by locating the SSH key seeding entry point and compare its handling of authorized_keys with the available .pub key. Done means a system without inbound SSH or an existing authorized_keys file can seed access from id_xxx.pub without requiring temporary allowed keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100