Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Fix typo in “On Using Keys and Biometrics” page #1270

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typo in “On Using Keys and Biometrics” page #1270

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture/sec-apis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down