It has moved to packages/modules/Connectivity
BUG: 186628461
TEST: TH
Merged-In: I2ed1fb00a7780c488c40d27590f206031fe033f2
Merged-In: I2a7a181e65be8952f8044df845efa80b6134d416
Change-Id: I8d162386289fcd4dc5e7092c3ea836fb67641e9f
This commit allows IKEv2/IPsec VPN to propose more algorithms that
newly added in IpSecAlgorithm. Those new algorithms have stronger
security guarantees and better performances.
This commit also removes algorithm name validation because all
algorithms are URL encoded to ensure no special characters create
problems due to their use by VpnProfile for list or field delimiting
(e.g. rfc7539esp(chacha20,poly1305))
Bug: 185265778
Test: atest FrameworksNetTests, CtsNetTestCases
Test: All new algorithms are manually verified
Change-Id: I1de322c95aacc8924e95bcdbcfdbd1ec441de99c
This ensures only one JNI strong reference for the death recipient when
the same binder is used for multiple linkToDeath calls.
Test: atest CtsAlarmManagerTestCases
atest FrameworksCoreTests:BinderDeathDispatcherTest
atest FrameworksMockingServicesTests:AlarmManagerServiceTest
Bug: 186792832
Change-Id: Ieea2d8f4e495a4c4687378db9d0b8c6949a0406a
Merged-In: Ieea2d8f4e495a4c4687378db9d0b8c6949a0406a
Add a keylayout mapping to support gamepad buttons and axes on the
Amazon Luna controller.
Buttons and axes are mapped according to
https://www.kernel.org/doc/Documentation/input/gamepad.txt except for
the Alexa Push-To-Talk button which is mapped to MEDIA_RECORD.
Bug: 183990549
Test: used the "Gamepad Tester" app and https://gamepad-tester.com in
Chrome to verify all mappings work.
Change-Id: I1921e501eea0ce398b79a32809efa63456074ed5
Isolated processes can only access world readable optimized files.
In order to not penalize their execution, we mark any dex files they
load as usedByOthers. This will prevent speed-profile optimizations
which marks the optimized files private to the app process.
Test: DexManagerTests
Bug: 163018062
Merged-In: Ib041584926ea142f37993f434a728d90db30e9bc
Change-Id: Ib041584926ea142f37993f434a728d90db30e9bc
This commit allows IKEv2/IPsec VPN to propose more algorithms that
newly added in IKE library. Those new algorithms have stronger
security guarantees and better performance.
It also improves the cooperability with
NordVpn. Previously, IKEv2/IPsec VPN only proposes PRF-HMAC-SHA1
and PRF-AES128-XCBC. NordVpn always prefer PRF-AES128-XCBC over
PRF-HMAC-SHA1 for security reasons, but few NordVpn servers have
broken PRF-AES128-XCBC support which will cause VPN setup to fail.
Proposing more PRFs can reduce the chance of selecting a broken
algorithms.
This commit also switches to use IKE library defined constants
Bug: 185265778
Test: atest FrameworksNetTests, CtsIkeTestCases
Test: new algorithms are manually tested
Change-Id: Id0983d4b73691b153ee0f1cf3bf63b215098a29a
- Create a new XML tag for the new format. The new format should
persist the arrays of values without assuming they necessarily
have different bits.
- Upon reading, if the new tag is present, use that. If the new
tag is not present but the old tag is present, then limit the
contents to the capabilities/transports that existed in R.
- Catch all exceptions and ignore the requests if they can't be
re-read from disk. This is a measure to avoid any mistake where
the device couldn't boot when JS tries to restore state.
Bug: 183071974
Test: atest JobStoreTest
Change-Id: I56cde50d2adab81134c8be4f6996d68018f4212a
When apps try to call factoryReset to do networking reset, it
will result in updating the setting in SettingsProvider.
ContentProvider will verify if the package name of the caller
that initiated the request being processed on the current thread.
The package should belong to the calling UID. The setting update
started from the ConnectivityService context, so the package will
be android but the calling UID will be the calling app. It will
cause a SecurityException. The behavior is fine previously as its
known caller(Settings) shares system UID. But it will be a
problem for other callers, such as CTS. Thus, clear the identity
since the necessary permission check should be examined at the
top of the method. The following actions should be fine to be
proceed from the system itself. Also replace the user restriction
check via hasUserRestrictionForUser with the UserHandle created
from the calling uid to ensure it's verified with correct user.
Bug: 186061922
Test: Factory reset from Settings
Change-Id: If2dd69f702a1eafff331f9e71f6b92aeadfb715d
We could implement the right thing easily with streams, but we're not
allowed to use streams in this context, and it doesn't seem worth the
bother of doing it any of the hard ways, given that we've only seen this
once in the year the code's been doing this.
Bug: https://issuetracker.google.com/169836837
Test: treehugger
Change-Id: I4ee29916c1b335bebecfe7f72e74ff71e8a24228
Set the compiler reason to 'cmdline' when the compilation was
initiated from cmdline. This will effectivively eliminate the
'unknown' reason from our metrics (except in some corner cases)
Test: adb shell cmd compile ...
Bug: 188655918
Change-Id: I0cb6e9182530bc2d88975af185a0a8256fae2c2c
This grants the shell app the SUGGEST_EXTERNAL_TIME permission needed
for the TimeManagerTest (CTS) to invoke the
TimeManager.suggestExternalTime() method during tests.
Bug: 184947690
Bug: 177079827
Test: See associated cts change
Merged-In: Ia1995ec9503dbd2b12e0b5b5f92a96e02f85beec
Change-Id: Ia1995ec9503dbd2b12e0b5b5f92a96e02f85beec
