Quoting Nicolas Belouin (nicolas@xxxxxxxxxx): > with CAP_SYS_ADMIN being bloated, the usefulness of using it to > flag a process to be entrusted for e.g reading and writing trusted > xattr is near zero. > CAP_TRUSTED aims to provide userland with a way to mark a process as > entrusted to do specific (not specially admin-centered) actions. It > would for example allow a process to red/write the trusted xattrs. You say "for example". Are you intending to add more uses? If so, what are they? If not, how about renaming it CAP_TRUSTED_XATTR? What all does allowing writes to trusted xattrs give you? There are the overlayfs whiteouts, what else? -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
