-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Domain set objects over 1024 bytes crash Dnsmasq #877
Comments
Fix applied for NS7 is not applicable in this scenario, because rules can handle only one set. I suggest to just add a validator inside the UI. |
We need to split the single domain set into multiple sets and create a rule for every set. |
Splitting the rules means managing one rule from the UI that translates to multiple rules inside UCI: this is not possible by design. |
Testing version Test case Verify the bug is no longer reproducible |
After more thorough testing, it appears 1024 is too high as a maximum value, since additional characters will be included in /var/etc/dnsmasq.conf. Gonna submit a PR setting the maximum to 960 for safety. |
This comment has been minimized.
This comment has been minimized.
Ensure the total number of characters a domain set uses in the dnsmasq configuration file does not exceed 1024 characters. NethServer/nethsecurity#877
The validation of the maximum characters used by a domain set in the dnsmasq configuration file is now handled on the backend. NethServer/nethsecurity#877
Ensure the total number of characters a domain set uses in the dnsmasq configuration file does not exceed 1024 characters. NethServer/nethsecurity#877
The validation of the maximum characters used by a domain set in the dnsmasq configuration file is now handled on the backend. NethServer/nethsecurity#877
Updated testing version: 23.05.5-ns.1.3.0-31-g6a6ff7e |
If the total size of domain names exceeds 1024 bytes Dnsmasq refuses to start (syntax error).
Steps to reproduce
Expected behavior
Dnsmasq running
Actual behavior
Dnsmasq stopped, name resolution broken
See also
We found and fixed the problem in NethServer 7:
NethServer/nethserver-squid@931f391
The text was updated successfully, but these errors were encountered: