This provides better conceptual naming alignment with other
-compat flags.
Signed-off-by: Daniel P. Berrangé <[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 75e39caedea..e211fdd2344 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 dfa3fea0577..f28c24149c8 100644
--- a/qapi/compat.json
+++ b/qapi/compat.json
@@ -77,7 +77,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)
#
# Since: 6.0
@@ -87,4 +87,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 f81a171a5b1..e6f3006b16c 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.56.0
