Page MenuHomePhorge

Implement Client integration for verification
Needs ReviewPublic

Authored by tusooa on Thu, Mar 19, 8:05 PM.
Tags
None
Referenced Files
F54658461: D295.1775001581.diff
Mon, Mar 30, 4:59 PM
F54590931: D295.1774989522.diff
Mon, Mar 30, 1:38 PM
F54560166: D295.1774984044.diff
Mon, Mar 30, 12:07 PM
F54489379: D295.1774971283.diff
Mon, Mar 30, 8:34 AM
F54449518: D295.1774964173.diff
Mon, Mar 30, 6:36 AM
F54341798: D295.1774944813.diff
Mon, Mar 30, 1:13 AM
F54341755: D295.1774944805.diff
Mon, Mar 30, 1:13 AM
F54341679: D295.1774944794.diff
Mon, Mar 30, 1:13 AM
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