52b8c9321b
When a database is set once it will still maintain that setting even if on the next connection it is not specified. Any databases that set the wal flag will need to turn the database back to its default when the flag is disabled or there will be an error in the access of the database. Bug: 314419678 Test: atest keystore2_test && atest legacykeystore_test Change-Id: I008f2d2f6ac055704b721cdd451fc8bdfe448832
25 lines
No EOL
710 B
Text
25 lines
No EOL
710 B
Text
package: "android.security.keystore2"
|
|
|
|
flag {
|
|
name: "wal_db_journalmode_v3"
|
|
namespace: "hardware_backed_security"
|
|
description: "This flag controls changing journalmode to wal"
|
|
bug: "191777960"
|
|
is_fixed_read_only: true
|
|
}
|
|
|
|
flag {
|
|
name: "disable_legacy_keystore_put_v2"
|
|
namespace: "hardware_backed_security"
|
|
description: "This flag disables legacy keystore put and makes it so that command returns an error"
|
|
bug: "307460850"
|
|
is_fixed_read_only: true
|
|
}
|
|
|
|
flag {
|
|
name: "import_previously_emulated_keys"
|
|
namespace: "hardware_backed_security"
|
|
description: "Include support for importing keys that were previously software-emulated into KeyMint"
|
|
bug: "283077822"
|
|
is_fixed_read_only: true
|
|
} |