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
Usually when people want to allow a device connecting to the system, they would like to allow it connecting at whatever path (as they plug it in different ports or sometimes use hubs, docks, etc). Today they have to edit the rules file manually to remove the parent-hash after adding the device. It would be nice if there was a way to not include it in the rules file in the first place.
The text was updated successfully, but these errors were encountered:
IIRC generate-policy -X does something like that. We need to introduce similar flags for the command or invent some filter mechanism without changing the default behavior.
Usually when people want to allow a device connecting to the system, they would like to allow it connecting at whatever path (as they plug it in different ports or sometimes use hubs, docks, etc). Today they have to edit the rules file manually to remove the
parent-hash
after adding the device. It would be nice if there was a way to not include it in the rules file in the first place.The text was updated successfully, but these errors were encountered: