-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
Move away from using privileged
for device mounts
#247
Comments
The requirements for this are still a good bit above my (current) level... There's a related issue for Z-Wave to MQTT here - although it's for the non JS version, I believe the same would apply |
@tprelog I think you heavily underestimate your current level... it's nothing more than adding capabilities using:
I think you're pretty decent in wiki hunting for the right capabilities ;-) Indeed like the link, linked in your link: The things is: privileged gives ALL permissions, even if we half them thats a win security wise. Don't worry it's not something that needs to be rushed though ^^ But I also think it's something that might be of interest for you in the long run, considering usb devices are quite relevant for Zwave and HASS. |
Research indicates the following: However: The supplementalGroups feature has been added to staging (#216) and hence this can be closed! |
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists |
Is your feature request related to a problem? Please describe.
Currently we use/advice privileged for basic device mounts.
This is bad advice and a significant security concern.
Describe the solution you'd like
Need to find and set the correct securityContext capabilities as needed for mounting devices.
The text was updated successfully, but these errors were encountered: