From f284d49293aead609de5b83d601260cfd86b7978 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Tue, 31 Jul 2012 09:46:52 -0700 Subject: docs: fix broken links Change-Id: I0523fb8eb8608b07cf7ca866d0c2ccfcbfc2e946 --- docs/html/guide/practices/security.jd | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'docs/html/guide/practices/security.jd') diff --git a/docs/html/guide/practices/security.jd b/docs/html/guide/practices/security.jd index 48ccdeb..ce59a9d 100644 --- a/docs/html/guide/practices/security.jd +++ b/docs/html/guide/practices/security.jd @@ -134,9 +134,8 @@ dynamic permission grants on a case-by-case basis.

To provide additional protection for sensitive data, some applications choose to encrypt local files using a key that is not accessible to the -application. (For example, a key can be placed in a KeyStore and -protected with a user password that is not stored on the device). While this +application. (For example, a key can be placed in a {@link java.security.KeyStore} +and protected with a user password that is not stored on the device). While this does not protect data from a root compromise that can monitor the user inputting the password, it can provide protection for a lost device without file system @@ -716,8 +715,7 @@ href="{@docRoot}reference/android/accounts/AccountManager.html"> AccountManager using checkSignature(). Alternatively, if only one application will use the credential, you might use a -KeyStore for +{@link java.security.KeyStore} for storage.

@@ -751,8 +749,8 @@ href="{@docRoot}reference/javax/crypto/KeyGenerator.html"> number generator significantly weakens the strength of the algorithm, and may allow offline attacks.

-

If you need to store a key for repeated use, use a mechanism like KeyStore that +

If you need to store a key for repeated use, use a mechanism like + {@link java.security.KeyStore} that provides a mechanism for long term storage and retrieval of cryptographic keys.

-- cgit v1.1