- Use List<Byte> since using uint8_t in radio
Bug: 183738486
Test: make
Change-Id: I5a52bc20ebd9c5ce000abd8588f2969d84c6bcd0
Merged-In: I5a52bc20ebd9c5ce000abd8588f2969d84c6bcd0
Connectivity CTS tests were moved from cts/tests/net to
packages/modules/Connectivity.
Bug: 185751610
Change-Id: Id4efd99c419706a52ad5d708888097bd6312d4e6
Test: treehugger is needed to test
Delay execution of any zygote command that may end up forking USAPs
until we've released our own ZygoteCommandBuffer. Otherwise we fork
the child with an open ZygoteCommandBuffer, preventing it from
opening its own.
Bug: 182084594
Test: Build and boot AOSP, with USAPs enabled and disabled.
Change-Id: I2366367d2155a120092fbdcae13cbb3d7f4e1d16
ServicePermissionsTest#testDumpProtected expects to see nothing
from dump() if the caller does not have the required permission.
After the refactor the ConnectivityService#dump(). It does not
leak real information for those callers without permission but
show the title of dumpsys, i.e. it shows "DUMP OF SERVICE HIGH
connectivity". This breaks the test since the test expects to
see nothing.
Move the permission check to the front of dump call stack since
there is no way to call other private dump related methods.
Bug: 185425662
Test: atest android.security.cts.ServicePermissionsTest
Test: adb shell dumpsys connectivity
Change-Id: I173c968a4f1c4d6f618ed87725a6ccda8d309988
Currently the RebootEscrowProvider is created as part of the boot
process, when device tries to restore the escrow data. This will
fail the first RoR boot attempt after we switch from HAL based
-> server based. So revisit the logic to reduce the time for
RebootEscrowManager to hold the provider in RAM.
Now we attempt to create a new provider object when
1. new RoR preparation request
2. load / restore escrow data (after reboot)
3. clear rebootescrow, as we want to clear provider's internal data
4. lskf capture
We reuse the old provider in memory when
1. arm reboot escrow, right before reboot (we don't switch the provider
after lskf is captured)
we clear the provider in memory when
1. after clear rebootescrow, so new RoR request can create a new one
2. after we finish restoring escrow data
Bug: 184676743
Test: unittest, cts test
Change-Id: I2109cbe69f0ebba766aabf30feb141053496354f
Hide until we can encode complicated structures like this
in something like a parcelable.
Bug: 182370110
Test: manual
Change-Id: I1797da52bfd447f198b48bd163b1bd0944aadb58
CryptoObject still called the legacy AndroidKeystoreProvider which did
not return the correct operation handle for per operation auth bound
keys.
Bug: 184804041
Bug: 185181377
Test: CtsVerifier->Security->Biometric Tests->2a Strong Biometrics +
Crypto
Merged-In: I0bceff0425e7ef32c394f33deda3c78f729c0c6c
Change-Id: I0bceff0425e7ef32c394f33deda3c78f729c0c6c
* Mock out registerReceiverAsUser() to avoid SecurityException
* Mock out setKeystorePassword() to not call into the real keystore
Bug: 170661840
Test: atest com.android.server.locksettings
Change-Id: I97c33f3b21ac16d2bb92e1658c222e4d0fd1970e
The shell *already had* the privileges granted by this permission due to
specific code in netd, and it lost those privileges when it gained the
CHANGE_NETWORK_STATE permission. Explicitly add
CONNECTIVITY_USE_RESTRICTED_NETWORKS so that it can obtain sufficient
permission in netd no matter CHANGE_NETWORK_STATE is set or not.
Remove a duplicate row by the way.
Bug: 185071689
Test: atest NetdClientTest#protectFromVpnTcp6
Change-Id: I64bc321de2c83378ce7bc8d9eb3044ae7772faca
If a method is called by adb command "service call"
with no parameters. It will cause to crash because
of a null object reference.
Add a null check for them to avoid system server crash.
Bug: 172885426
Test: FrameworksNetTest
adb shell service call connectivity #
Change-Id: I8748fc5c6a7a6e82db3581e3026a3f75909a357e
