we need "insecure remote test terminal" to test on real hardware without invalidating measurements
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
Need to implement remote ssh access to hardware with explicit board config/config setting, otherwise really exhausting testing
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 identifying the existing board configuration and test entry points in the heads repository, then determine where an explicit insecure remote-terminal setting belongs. Done means remote SSH access to the selected hardware is available for testing without invalidating measurements, while remaining opt-in through board configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100