Skip to content
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

Option whitelist / Rouge DHCP replies #422

Open
incognico opened this issue Dec 6, 2024 · 2 comments
Open

Option whitelist / Rouge DHCP replies #422

incognico opened this issue Dec 6, 2024 · 2 comments

Comments

@incognico
Copy link

Is there some way to have a option whitelist? Currently there is "option", which tells dhcpcd which ones to request. Also there is "nooption" which acts as a blacklist for options in the reply. But all (not explicitly requested) options in the reply which are not blacklisted via "nooption" will get accounted for.

Would be nice to either have something like "allowoptions" as a whitelist or a config parameter to enable a behaviour that only the explicitly requested options get respected in a reply and any surplus ones get discarded.

@rsmarples
Copy link
Member

What you could do is supply your own dhcpcd-definitions.conf and re-compile dhcpcd using it. Any options not in your list won't be exported to the environment.

That won't stop dhcpcd from using what it understands via code however. Does that meet your needs for the time being?

@incognico
Copy link
Author

incognico commented Jan 15, 2025

That seems to do the job. Would calling exit in the entry hook achive the same, or will dhcpcd do some more unwanted stuff on its own, in contrast to a stripped dhcpcd-definitions.conf?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants