The Key{Mint,Master} spec previously said that RSA-PSS mode should use
SHA-1 for the MGF1 digest, separately from whatever Tag::DIGEST gets
specified as the main digest.
However, both the reference implementation and the VTS/CTS tests
use BoringSSL's defaults, which is to re-use the main digest as the MGF1
digest if none is separately specified.
Given that this behaviour is embedded in many implementations over
several years (and given that there isn't a security implication),
change the spec to match this behaviour. Also update the VTS test
code to make this clear/obvious.
Test: VtsAidlKeyMintTargetTest, VtsHalKeymasterV4_0TargetTest
Bug: 210424594
Change-Id: I4303f28d094ef4d4b9dc931d6728b1fa040de20d
Ignore-AOSP-First: target internal master first due to merge conflict
This reverts commit 37c5495c52.
This "clarification" was in fact a change of the HAL interface,
introducing a new requirement which was not present in earlier
Android releases. There are devices on the market that switch
seamlessly between configs that differ in resolution and DPI,
and therefore have those configs in a config group.
Bug: 200184776
Test: m
Change-Id: I5bba1c6532f5f46da874385164a0bc0cc0435225
setContentType can be called even if it's not supported.
On some devices this surves as a signal to disable on-device
post processing in order to reduce latency.
Bug: 202007307
Test: n/a
Change-Id: I9888d48979cd2442b54054730c78cf7b4ed6aab4
Allow camera providers to advertise the mapping between device state
and camera orientation.
Bug: 201005727
Test: VtsHalCameraProviderV2_4TargetTest
--gtest_filter=PerInstance/CameraHidlTest.getCameraCharacteristics/0_internal_0
Change-Id: Ibb035f4dc3d8af1106ac08f86e43b953ddcbf55b
It now specifies that the micrometers-per-wheel-tick values are static
and approximations.
Test: None
Bug: 169364681
Change-Id: Ia002bdcf7c9a91d82d8f6d543d2476d227256046
Merged-In: Ia002bdcf7c9a91d82d8f6d543d2476d227256046
(cherry picked from commit c0653a4452)
It now specifies that the micrometers-per-wheel-tick values are static
and approximations.
Test: None
Bug: 169364681
Change-Id: Ia002bdcf7c9a91d82d8f6d543d2476d227256046
This is a change in behaviour for EPOCH_TIME to align it with a future revisions.
Bug: 157504928
Test: atest CarServicesTest
Test: atest VehiclePropertyIdsTest
Change-Id: I81881a03a1a562afc93cb1a2fe8a8fffa43f093d
This CL adds a comment that discourages use of this interface. The AIDL
interface, IFingerprint, should be used instead.
Bug: 160189286
Test: hidl-gen -L check android.hardware.biometrics.fingerprint@2.3::IBiometricsFingerprint
Change-Id: Ifafb191ac16e03e60d677fce6dc9e41e87bad0c0
This is used on cuttlefish for tests, and so it has to be frozen like
1.0 in order to avoid having to add an exception to the test (which is
considered the worst of all bad solutions here).
Bug: 191115626
Test: build (hash correctness check is done at build time)
Change-Id: I3bbe18e6f6e21c39f8e5efd0ddcbfb0c66385f8c
Freeze vehicle hal interface for android s.
Bug: 157608908
Test: atest vts_treble_vintf_vendor_test
Change-Id: I092f7c7facbb08f381560840c449ae1211625c65
Adding TEST_PATTERN_MODE_BLACK to support the new sensor privacy
feature on more limited-capability camera implementations.
Also updating older docs due to an API being moved to public.
Test: Camera CTS continues to pass
Bug: 189507251
Change-Id: I043d011ad43070d6c402cdffbff3d2e9b70ffd7b
Currently, vendors are asked to duplicate old events to onEvent()
and onEvent_1_1(). This is not the typically way other modules
would do. Thus, remove the requirement of duplicate events,
and replace it with only firing onEvent_1_1 when feasible.
Note no VTS is added currently, from vendor feedback, there is
no reliable way to guarantee the callbacks will be called in the
test.
Test: hidl-gen -L hash -r android.hardware:hardware/interfaces \
android.hardware.tetheroffload.control@1.1
Bug: 149467454
Merged-In: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
Change-Id: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
(cherry-picked from ag/14408065)
Currently, vendors are asked to duplicate old events to onEvent()
and onEvent_1_1(). This is not the typically way other modules
would do. Thus, remove the requirement of duplicate events,
and replace it with only firing onEvent_1_1 when feasible.
Note no VTS is added currently, from vendor feedback, there is
no reliable way to guarantee the callbacks will be called in the
test.
Test: hidl-gen -L hash -r android.hardware:hardware/interfaces \
android.hardware.tetheroffload.control@1.1
Bug: 149467454
Change-Id: I75c1a7788e5d48fb3e2836d54b4fd854c0247214
