UVM Extension Editorial Change

[apowers313]

The UVM Extension text currently includes the following:

Authenticator processing
The authenticator augments the authenticator data with a user verification index indicating the method used by the user to authorize the operation, as defined below. This extension can be added to attestation objects and assertions.

Note the mention of user verification index, which was probably copied from the UVI extension. I'm not sure if the fix is as simple as changing index to mode or if the whole section should be re-written.

[selfissued]

Note that PR #389 changed "mode" to "method", fixing issue #411 . I understand that this doesn't address the confusion between "index" and "method". The owner of this extension ( @rlin1 ?) should review the text and propose a fix.

[equalsJeffH]

good catch @apowers313, thx.

I propose this fix:
The [=authenticator=] sets the [=authenticator extension output=] to be a uvmFormat structure indicating (any or all of) the user verification method employed for the [=authorization gesture=], the [=authenticator=]'s key protection type and/or matcher protection type.

[ I am now guessing that @rlin1 had named this extension "user verification mode" (rather than UV "method") because it can convey more information that just the UV Method employed. ]

[selfissued]

Sounds fine to me

[nadalin]

@selfissued @rlin1 please create a PR and merge

[rlin1]

see #675

[equalsJeffH]

this was fixed by PR #675 as noted by @rlin1 #368 (comment). Closing.