Shikha Panwar 3d33a135ad Secretkeeper/VTS: Per-connection replay protection
Add test coverage for replay protection in Secretkeeper. Test that:
1. Sk implementation encrypts/decrypts messages using correct
sequence_numbers.
2. Out of order messages are not accepted.
3. The sequence numbers are per-connection ie, new SeqNum is used for a
   fresh connection.

Also, refactor code. SeqNumbers are maintained by
libsecretkeeper_client. Have sk_client use a handle to SkSession for
SecretManagement requests. Replay protection tests however require more
fine grained control of SeqNums. For these we have introduced
`secret_management_request_custom_aad()` method.

Bug: 316126411
Test: atest VtsSecretkeeperTargetTest
Change-Id: I385856c04e185d2b300d59a1b54cb8f09cbf836f
2023-12-20 14:41:09 +00:00
2023-09-13 21:18:46 +00:00
2023-09-08 20:25:29 +00:00
2023-12-19 00:37:36 +00:00
2023-10-10 10:30:03 +09:00
2023-10-10 16:17:14 -07:00
2023-04-07 23:41:20 +00:00
2023-09-19 23:48:35 +09:00
2023-04-07 23:41:20 +00:00
2023-12-12 18:06:34 +09:00
2023-09-11 16:21:52 +00:00
2023-09-15 13:16:28 +09:00
2023-09-08 21:06:03 +00:00
2023-12-12 08:03:20 +00:00
2023-09-11 17:03:06 +00:00
2023-12-08 16:37:09 +05:30
2023-09-11 16:32:19 +00:00
2021-10-28 22:04:46 +00:00
2016-08-30 11:28:36 -07:00
2022-08-01 16:19:14 +00:00
2021-01-21 15:06:51 +09:00
Description
No description provided
134 MiB
Languages
C++ 56.3%
AIDL 41.2%
C 1.5%
Rust 0.4%
Java 0.4%
Other 0.1%