Bug 1256829 - [RFE] Restrict docker functions based on key used to sign image
[RFE] Restrict docker functions based on key used to sign image
Status: ASSIGNED
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker (Show other bugs)
7.2
x86_64 Linux
low Severity low
: rc
: ---
Assigned To: Miloslav Trmač
atomic-bugs@redhat.com
: Extras, FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-25 10:27 EDT by Jake Hunsaker
Modified: 2017-08-02 02:58 EDT (History)
5 users (show)

See Also:
Fixed In Version: nalin@redhat.com
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jake Hunsaker 2015-08-25 10:27:18 EDT
This is an RFE from talking with customers at Container Con.


During Container Con, Docker presented the ability to sign docker images and thus allow a user to trust that an image is valid. In this same vein rkt demonstrated similar capabilities and spoke about how they are looking to expand this to allow/disallow certain actions based on the level of trust given to a particular key.

Docker should provide this kind of control as well. 

For example, if an image was signed with key A that the user trusts for network operations, but not for storage operations then docker could be configured to refuse to start a container if the user was trying to volume-mount something into the container. However, if the image was signed with key B that the user "trusts more", then docker would allow the volume-mount.

Note You need to log in before you can comment on or make changes to this bug.