LizardByte / LizardByte/roadmap
Sunshine: Find a way to secure the local HTTPS (no self signed certificate warning)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Description
### Is there an existing issue for this item?
- [x] I have searched the existing issues
### Repositories
LizardByte/Sunshine
### Languages/Skills/Technologies
_No response_
### Description
The idea is to find a way to remove the HTTPS scare screen during the setup process (by e.g. trusting the HTTPS cert)
### Estimated Effort
effort:Large
### Priority
priority:Low
### Target Milestone
6+ months
### Dependencies
_No response_
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 reviewing Sunshine's setup process and how its local HTTPS certificate is presented during initial configuration. Compare feasible ways to establish trust without the self-signed certificate warning, and consider the platform and security implications; the work is done when setup no longer shows the warning through an agreed approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100