Bug #497
Users can do too much in DNS config
| Status: | Closed | Start date: | 04/01/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Walter Secco |
% Done: | 100% |
|
| Category: | - | Spent time: | 2.00 hours | |
| Target version: | 6.1.6 | |||
| Affected version: | Operating System: | |||
| Resolution: | Resolved | Architecture: | ||
| Reproduceable: |
Description
One user added * as A entry.
Another user added something like this:
google-site-verification=bKkc59x1ZGV6XyuUliq-vmkzRb4g7fPzc7M1XKnyA_U': label too long
as NS entry.
Such entries can bring the whole DNS server down.
It should be more verified.
Associated revisions
Issue #497: Add some character validate checks
History
Updated by Danny Terweij about 1 year ago
- Priority changed from Normal to Low
- Resolution set to Not a Bug
An * as a A record is valid.
The google verify line is valid as TXT if i am right, but not as NS.
Also its your job as System Admin to fix problems if in this case your DNS Server failed.
The only thing that be can done is to disallow a = sign in the NS input field.
Updated by Danny Terweij about 1 year ago
- Target version set to 6.1.6
- Resolution deleted (
Not a Bug)
Updated by Danny Terweij 12 months ago
- Priority changed from Low to Normal
I can not find a location within the sources where to add a valid char check. Some other developer or someone from the community has to take a look into this.
Updated by Walter Secco 12 months ago
- Assignee set to Walter Secco
- % Done changed from 0 to 10
Updated by Danny Terweij 11 months ago
- Status changed from New to Closed
- % Done changed from 10 to 100
- Resolution set to Resolved
Fix submitted into 6.1.x branch. Not into trunk (will break new dns features so need to investigate how to implement it in trunk).
Updated by zynefemail zynefemail 3 months ago
Thanks for this fixable airman - I harmonize your wreak ! Make on penning.
DetectiveUnlimited.com