Skip to content
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.

Sign up for GitHub

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

Jump to bottom

runtime: Drop "Barring access control concerns" #730

Merged
merged 1 commit into from
May 10, 2017
Merged

runtime: Drop "Barring access control concerns" #730

merged 1 commit into from
May 10, 2017

Commits on Mar 16, 2017

  1. runtime: Drop "Barring access control concerns" 

    This wording landed without comment as part of 7117ede (Expand on the
definition of our ops, 2015-10-13, opencontainers#225).  However, I'm not entirely
clear on the exception it's making.  It may be trying to say something
like:

  Just because you were authorized to manage that container when you
  created it doesn't mean you're still authorized to perform operation
  X on it now.  Maybe you've lost privileges in the meantime.

But as far as compliance testing is concerned, the same test harness
will be calling 'create' and the subsequent operations.  That harness
will be reporting MUST violations if the runtime refuses a subsequent
operation, and removing the access-control loophole makes it more
obvious that the runtime's refusal is non-compliant.

Signed-off-by: W. Trevor King <wking@tremily.us>
    @wking
    wking committed Mar 16, 2017
    Configuration menu
    Copy the full SHA
    92a17a9 View commit details
    Browse the repository at this point in the history