Feature or enhancement
Proposal:
I'd like to spin up k8s pods that use the netrc for authentication to various endpoints, since the requests module supports it implicitly.
However, still as of now, k8s secrets can't be mounted with a specified user, only specified group. This means that when our ~/.netrc is owned by root, belongs to the same group as our user and still can be read because its ACLs are 640, the following code will still fail:
import netrc
x = netrc.netrc()
I think that the security check should permit the following scenarios:
- We are user
foo, the rights for ~/.netrc are -rw------- at the most, and the ~/.netrc belongs to user foo and whatever group. It doesn't matter, we are the sole owner of the file.
- We are user
foo who belongs to group bar, the rights for the ~/.netrc are -rw-r----- at the most, and the ~/.netrc belongs to user root and group bar. As members of the same group, we are clearly allowed to use it.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Feature or enhancement
Proposal:
I'd like to spin up k8s pods that use the netrc for authentication to various endpoints, since the
requestsmodule supports it implicitly.However, still as of now, k8s secrets can't be mounted with a specified user, only specified group. This means that when our
~/.netrcis owned by root, belongs to the same group as our user and still can be read because its ACLs are 640, the following code will still fail:I think that the security check should permit the following scenarios:
foo, the rights for~/.netrcare-rw-------at the most, and the~/.netrcbelongs to userfooand whatever group. It doesn't matter, we are the sole owner of the file.foowho belongs to groupbar, the rights for the~/.netrcare-rw-r-----at the most, and the~/.netrcbelongs to userrootand groupbar. As members of the same group, we are clearly allowed to use it.Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response