Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Check necessity of CAP_SYS_ADMIN and CAP_NET_ADMIN capabilities. #7

Open
4 tasks
jmuchovej opened this issue May 4, 2021 · 0 comments
Open
4 tasks

Comments

@jmuchovej
Copy link
Owner

Binding to port 53 seems to require CAP_NET_BIND_SERVICE.

Further, having ZeroTier run within the container appears to require CAP_SYS_ADMIN and CAP_NET_ADMIN. Based on my understanding of cap_addCAP_SYS_ADMIN should include CAP_NET_ADMIN... but, CAP_SYS_ADMIN also gets pretty close to root's capabilities – which (ideally) isn't necessary.

  • Need to develop a better understanding of CAP_SYS_ADMIN.
  • Need to develop a better understanding of CAP_NET_ADMIN.
  • Test what capabilities are required for running CoreDNS, strictly.
  • Test what capabilities are required for running ZeroTier, strictly.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant