openscopeproject / openscopeproject/TrguiNG
Option to accept self-signed/invalid SSL certificates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 796
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
Problem
When running Transmission behind a reverse proxy with a self-signed certificate, TrguiNG cannot connect because the reqwest client performs strict certificate validation against the system trust store.
The connection fails with the equivalent of: SSL certificate problem: unable to get local issuer certificate
The predecessor (transgui) did not perform certificate validation at all, so these setups worked out of the box.
Proposal
Add a per-connection toggle to accept invalid/self-signed certificates.
Happy to submit a PR for this if approved.
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
Start by locating the reqwest client and the per-connection settings in TrguiNG, then trace how connection options reach the client. Done means a per-connection toggle can allow self-signed or otherwise invalid certificates while the existing strict validation remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- desktop, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100