Page MenuHomePhorge

Implement Client integration for verification
Needs ReviewPublic

Authored by tusooa on Thu, Mar 19, 8:05 PM.
Tags
None
Referenced Files
F53841716: D295.1774854499.diff
Sun, Mar 29, 12:08 AM
F53764688: D295.1774840022.diff
Sat, Mar 28, 8:07 PM
F53722128: D295.1774832409.diff
Sat, Mar 28, 6:00 PM
F53709587: D295.1774830144.diff
Sat, Mar 28, 5:22 PM
F53694823: D295.1774827531.diff
Sat, Mar 28, 4:38 PM
F53678760: D295.1774824694.diff
Sat, Mar 28, 3:51 PM
F53665819: D295.1774822267.diff
Sat, Mar 28, 3:11 PM
F53647890: D295.1774819090.diff
Sat, Mar 28, 2:18 PM
Subscribers
None

Details

Reviewers
None
Group Reviewers
O1: the Kazv Project
Maniphest Tasks
T156: SAS verification
Summary

This is part 3 of https://iron.lily-is.land/T156 . It implements an integration layer in Client for device verification. The layer handles the receiving and sending of verification events.

The unit tests in verification-processing-test.cpp are adapted from an output of OpenCode.

Type: add

Test Plan

To be tested together with the corresponding diff in kazv.

Diff Detail

Repository
rL libkazv
Branch
tusooa/stacked-2
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 587
Build 1156: Invoke BuildbotBuildbot build #1494
Build 1155: arc lint + arc unit

Event Timeline

Still work in progress. Also missing tests.

Harbormaster returned this revision to the author for changes because remote builds failed.Thu, Mar 19, 8:30 PM
Harbormaster failed remote builds in B572: Diff 887!

add EnsureKeysForDevicesAction

add missing implementations

Mark devices as verified when we want to send a done event

Prevent updating keys overriding trust level