rustdesk / rustdesk/rustdesk-server
Option to disable check for new version call to https://api.rustdesk.com/version/latest
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
First of all, thanks for this great software.
Is your feature request related to a problem? Please describe.
It is not a super big issue but still I want to address it.
Since february the hbbs server has been calling https://api.rustdesk.com/version/latest, once a day, without any entry in the log that a new version is present. This is most likely just a feature that will be implemented on the api server side or maybe my icinga update check informed me faster and I did the update before the api call could receive a vaild update url.
Describe the solution you'd like
Option A)
Add a parameter to overwrite the update check url "https://api.rustdesk.com/version/latest"
Option B)
Add a parameter to opt-in or opt-out the version check.
Describe alternatives you've considered
Put api.rustdesk.com in /etc/hosts.
Add an outgoing firewall rule
Additional context
If there is chance that Option A will be implemented it would also be nice to have a description of the api interface of https://api.rustdesk.com/version/latest so this can be implemented locally.
Best Regards
Nicolas
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 tracing where the hbbs server makes its daily request to https://api.rustdesk.com/version/latest and where server options are defined. Compare the opt-out and URL-override proposals, then verify the selected behavior and document the version endpoint if local overrides are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100