KEYS: trusted: Fix migratable=1 failing
authorJarkko Sakkinen <jarkko@kernel.org>
Thu, 28 Jan 2021 23:56:20 +0000 (01:56 +0200)
committerJarkko Sakkinen <jarkko@kernel.org>
Tue, 16 Feb 2021 08:40:28 +0000 (10:40 +0200)
Consider the following transcript:

$ keyctl add trusted kmk "new 32 blobauth=helloworld keyhandle=80000000 migratable=1" @u
add_key: Invalid argument

The documentation has the following description:

  migratable=   0|1 indicating permission to reseal to new PCR values,
                default 1 (resealing allowed)

The consequence is that "migratable=1" should succeed. Fix this by
allowing this condition to pass instead of return -EINVAL.

[*] Documentation/security/keys/trusted-encrypted.rst

Cc: stable@vger.kernel.org
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>
Cc: David Howells <dhowells@redhat.com>
Fixes: d00a1c72f7f4 ("keys: add new trusted key-type")
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
security/keys/trusted-keys/trusted_tpm1.c

index 204826b..493eb91 100644 (file)
@@ -801,7 +801,7 @@ static int getoptions(char *c, struct trusted_key_payload *pay,
                case Opt_migratable:
                        if (*args[0].from == '0')
                                pay->migratable = 0;
-                       else
+                       else if (*args[0].from != '1')
                                return -EINVAL;
                        break;
                case Opt_pcrlock: