nextcloud / nextcloud/bruteforcesettings
Add whitelisted IP via hostname to support dyndns / dynamic IP address scenarios
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 18
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 21
Description
It might be useful to add an IP to whitelist based on a domain name. Think about the following scenario:
The user want's to whitelist connections from his home network ( = his public IP address). He already has a dyndns service running like eg. demouser.duckdns.org. This domain will resolve to his public IP.
It'd be nice if the user could add this domain to the whitelist which then gets (periodically) resolved to the wished IP.
This is probably pretty low on priority, but I wanted to mention the idea 😊
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
The issue names no files, tests, or entry points. Start by locating the existing IP whitelist implementation and its tests, then clarify how hostname resolution and periodic updates should work. Done means a dynamic-DNS hostname can be configured as a whitelist entry and remains synchronized with its resolved IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100