Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removing errant @hide annotation

Browse Source 
There is no reason that setIsStrongBoxBacked() should be hidden for
KeyProtection. Users should be expected to take advantage of using
StrongBox for protecting imported keys if they choose to.

Bug: 148901504
Test: doc string change
Change-Id: Ie906cb75fd853d3465ff066493c6df50d68d7e9c
This commit is contained in:
Max Bires
2020-02-11 22:11:14 -08:00
parent 95cb4043bb
commit d407c0be20
2 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
api/current.txt
View File

@@ -42914,6 +42914,7 @@ package android.security.keystore {
method @NonNull public android.security.keystore.KeyProtection.Builder setDigests(java.lang.String...);
method @NonNull public android.security.keystore.KeyProtection.Builder setEncryptionPaddings(java.lang.String...);
method @NonNull public android.security.keystore.KeyProtection.Builder setInvalidatedByBiometricEnrollment(boolean);
method @NonNull public android.security.keystore.KeyProtection.Builder setIsStrongBoxBacked(boolean);
method @NonNull public android.security.keystore.KeyProtection.Builder setKeyValidityEnd(java.util.Date);
method @NonNull public android.security.keystore.KeyProtection.Builder setKeyValidityForConsumptionEnd(java.util.Date);
method @NonNull public android.security.keystore.KeyProtection.Builder setKeyValidityForOriginationEnd(java.util.Date);

1
keystore/java/android/security/keystore/KeyProtection.java
View File

@@ -1031,7 +1031,6 @@ public final class KeyProtection implements ProtectionParameter, UserAuthArgs {
/**
* Sets whether this key should be protected by a StrongBox security chip.
* @hide
*/
@NonNull
public Builder setIsStrongBoxBacked(boolean isStrongBoxBacked) {