From: Daniel P. Berrangé <[email protected]> This provides better conceptual naming alignment with other -compat flags.
Signed-off-by: Daniel P. Berrangé <[email protected]> Message-ID: <[email protected]> Reviewed-by: Marc-André Lureau <[email protected]> Reviewed-by: Markus Armbruster <[email protected]> Signed-off-by: Markus Armbruster <[email protected]> --- docs/system/security.rst | 2 +- qapi/compat.json | 4 ++-- qapi/qapi-util.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/system/security.rst b/docs/system/security.rst index 75e39caede..e211fdd234 100644 --- a/docs/system/security.rst +++ b/docs/system/security.rst @@ -168,7 +168,7 @@ eligible for CVE assignment. Annotations will be extended to other backend and object types over time, to make their security status explicit. It is possible to control or identify the usage of types that do not offer -an explicit security boundary using the ``insecure-types`` parameter to the +an explicit security boundary using the ``insecure-input`` parameter to the ``-compat`` argument, which accepts three values: * accept: usage of any type will be permitted. This is the current diff --git a/qapi/compat.json b/qapi/compat.json index b183be15d4..7146eab6b9 100644 --- a/qapi/compat.json +++ b/qapi/compat.json @@ -73,7 +73,7 @@ # @unstable-output: how to handle unstable output (default 'accept') # (since 6.2) # -# @insecure-types: how to handle types that are not declared secure +# @insecure-input: how to handle types that are not declared secure # (default 'accept') (since 11.2) # # Limitation: @deprecated-input, @deprecated-output, @unstable-input, @@ -91,4 +91,4 @@ '*deprecated-output': 'CompatPolicyOutput', '*unstable-input': 'CompatPolicyInput', '*unstable-output': 'CompatPolicyOutput', - '*insecure-types': 'CompatPolicySecurity' } } + '*insecure-input': 'CompatPolicySecurity' } } diff --git a/qapi/qapi-util.c b/qapi/qapi-util.c index fe0a6a57c8..e5d8662f8b 100644 --- a/qapi/qapi-util.c +++ b/qapi/qapi-util.c @@ -72,7 +72,7 @@ bool compat_policy_check_security(const CompatPolicy *policy, return true; } - switch (policy->insecure_types) { + switch (policy->insecure_input) { case COMPAT_POLICY_SECURITY_ACCEPT: return true; -- 2.55.0
