You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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?
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.
The text was updated successfully, but these errors were encountered: