From edc90e0a97f050932189d46148c124fe63954d30 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Tue, 7 Sep 2021 12:41:20 +0100 Subject: [PATCH] Fix typo --- docs/architecture/sec-apis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/sec-apis.md b/docs/architecture/sec-apis.md index 84e3e0381..0ea00a601 100644 --- a/docs/architecture/sec-apis.md +++ b/docs/architecture/sec-apis.md @@ -10,7 +10,7 @@ Below are some findings on using a couple of security features in Android: The `AndroidKeyStore` is an implementation of the [Java Cryptography Architecture (JCA)](https://docs.oracle.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec.html)'s `KeyStore` service to manage application-specific cryptographic keys. Such keys can be created or imported with an associated label, then an opaque `Key` class obtained from that label to use for cryptographic operations. However, they **cannot** be exported. The remainder here focuses on creating rather than import. -Obtaining this Keystore is done using the static method `Keystore.getIstance()` and specifying the "AndroidKeyStore" Service Provider Interface (SPI) provider. +Obtaining this Keystore is done using the static method `Keystore.getInstance()` and specifying the "AndroidKeyStore" Service Provider Interface (SPI) provider. New keys are created using an instance of `KeyGenerator` (or `KeyPairGenerator`), again specifying "AndroidKeyStore" as the SPI provider. When creating a new key, several properties can be applied via `KeyGenParameterSpec`, including: