Push padding and digest handling down to specific key types.

AsymmetricKey handled checking for digest and padding, but that doesn't
make sense because not all asymmetric key types need both.  This is in
preparation for adding asymmetric encryption/decryption support.

Change-Id: I7b9a4fc37b6d31ab25c56015c1df7d114affe882

1 files changed, 0 insertions, 16 deletions

diff --git a/asymmetric_key.cpp b/asymmetric_key.cpp
index ba13cbf..d54570a 100644
--- a/asymmetric_key.cpp
+++ b/asymmetric_key.cpp
@@ -94,20 +94,4 @@ keymaster_error_t AsymmetricKey::formatted_key_material(keymaster_key_format_t f
     return KM_ERROR_OK;
 }
 
-Operation* AsymmetricKey::CreateOperation(keymaster_purpose_t purpose, keymaster_error_t* error) {
-    keymaster_digest_t digest;
-    if (!authorizations().GetTagValue(TAG_DIGEST, &digest) || digest != KM_DIGEST_NONE) {
-        *error = KM_ERROR_UNSUPPORTED_DIGEST;
-        return NULL;
-    }
-
-    keymaster_padding_t padding;
-    if (!authorizations().GetTagValue(TAG_PADDING, &padding) || padding != KM_PAD_NONE) {
-        *error = KM_ERROR_UNSUPPORTED_PADDING_MODE;
-        return NULL;
-    }
-
-    return CreateOperation(purpose, digest, padding, error);
-}
-
 }  // namespace keymaster