Implement other TLS certificate deployments
Open
Nobody has claimed this yet.
enhancement
low-prio
remote-access
- Dominant language
- Python
- Stars
- 38
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
- allow enabling TLS with own certificate
- allow DNS TXT record validation instead of web-challenge (might be covered by the own cert already?)
- allow using arbitrary "static domain" to allow LAN only arbitrary hostnames
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, tests, or entry points. Start by tracing the existing web-challenge TLS deployment, then assess each checklist item: own certificates, DNS TXT validation, and arbitrary static domains. Done means the supported deployment paths are implemented and their behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100