Re: [PATCH 2/2] ipe: also reject policy updates with the same version
From: Fan Wu <hidden>
Date: 2024-09-23 18:01:14
On 9/22/2024 6:56 AM, luca.boccassi@gmail.com wrote:
quoted hunk ↗ jump to hunk
From: Luca Boccassi <redacted> Currently IPE accepts an update that has the same version as the policy being updated, but it doesn't make it a no-op nor it checks that the old and new policyes are the same. So it is possible to change the content of a policy, without changing its version. This is very confusing from userspace when managing policies. Instead change the update logic to reject updates that have the same version with ESTALE, as that is much clearer and intuitive behaviour. Signed-off-by: Luca Boccassi <redacted> --- security/ipe/policy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)diff --git a/security/ipe/policy.c b/security/ipe/policy.c index 5de64441dfe7..01da3a377e7f 100644 --- a/security/ipe/policy.c +++ b/security/ipe/policy.c@@ -115,7 +115,7 @@ int ipe_update_policy(struct inode *root, const char *text, size_t textlen, goto err; } - if (ver_to_u64(old) > ver_to_u64(new)) { + if (ver_to_u64(old) >= ver_to_u64(new)) { rc = -ESTALE; goto err; }
Hi Luca, Can you elaborate more about the potential confusion for the userspace users? The policy version is currently used to prevent the activation of outdated or vulnerable policies (e.g., to avoid activating a policy trusting a compromised device). The version is not incremented unless a vulnerability is identified. Essentially, version comparison acts as a minimum threshold, ensuring only policies that meet or exceed this version can be activated. Additionally, the version check is performed in ipe_set_active_pol(), so it will need to be updated accordingly. The documentation should also be refreshed to reflect these changes and ensure consistency with the new version handling process. -Fan