diff options
| author | 2025-01-06 18:17:36 +0000 | |
|---|---|---|
| committer | 2025-01-06 23:49:42 +0000 | |
| commit | 231799e67c73addce251ba36c6f63b6b41da5c41 (patch) | |
| tree | 40e584fb43d315e4e59bbd2487c6abc8a9deb7f2 /libs/androidfw/AttributeResolution.cpp | |
| parent | 81036dbfaa3ddd4271909a2b26c927d1a0c454c9 (diff) | |
locksettings: use ArrayUtils.zeroize()
Since direct uses of Arrays.fill() can potentially be optimized out by
the compiler and also do not immediately clean the data cache, use
ArrayUtils.zeroize() instead which is more reliable.
Flag this fix, to comply with trunk-stable policies. As usual for
flags, the flag is temporary and will be removed soon.
This CL is just a straightforward replacement of existing zeroization
code. Later CLs will add missing zeroization in some places and
allocate arrays as non-movable as needed.
Bug: 320392352
Test: atest FrameworksServicesTests:com.android.server.locksettings
Flag: android.security.secure_array_zeroization
Change-Id: I9b9830ada97bc0a8cb0b661fd9bea0e54f925d2d
Diffstat (limited to 'libs/androidfw/AttributeResolution.cpp')
0 files changed, 0 insertions, 0 deletions