docs(19.5): record the last UAT answers (prohibitions, CR-02 wording)
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
---
|
||||
status: testing
|
||||
status: complete
|
||||
phase: 19.5-social-login-in-sm-user-plugin
|
||||
source: [19.5-VERIFICATION.md]
|
||||
started: 2026-10-21T00:24:54.347Z
|
||||
updated: 2026-10-21T13:20:00.000Z
|
||||
updated: 2026-10-21T13:40:00.000Z
|
||||
---
|
||||
|
||||
## Current Test
|
||||
@@ -30,18 +30,20 @@ retested_by: 19.5-05
|
||||
|
||||
### 3. Review the judgment-tier prohibition verdicts in the 'Prohibitions' section of this report (non-authoritative LLM-judge verdicts).
|
||||
expected: Confirm or dispute each verdict; all are recorded as no violation found.
|
||||
result: [pending]
|
||||
result: pass
|
||||
reported: "prohibitions ok"
|
||||
|
||||
### 4. Decide on 19.5-REVIEW CR-02: an account pre-created by sociallogin from an unverified provider email (created activated, S classes/registration.go) keeps the attacker's Microsoft or Facebook identity after the real owner proves the address with a reset-code password reset.
|
||||
expected: Either accept it (PHP parity on account creation) and correct sm-sociallogin-plugin README.md:50, which offers 'proves the address with a password reset' as the recovery; or schedule the follow-up the review proposes (create the account inactive unless p.EmailVerified, and/or drop unverified identities when the reset stamps email_verified_at).
|
||||
result: [pending]
|
||||
result: pass
|
||||
reported: "fix README wording quickly" (behaviour accepted; sm-sociallogin-plugin 79cebb9 says a reset does not unlink identities linked before the proof and points to the identities list)
|
||||
|
||||
## Summary
|
||||
|
||||
total: 4
|
||||
passed: 1
|
||||
passed: 3
|
||||
issues: 0
|
||||
pending: 2
|
||||
pending: 0
|
||||
skipped: 1
|
||||
blocked: 0
|
||||
|
||||
|
||||
Reference in New Issue
Block a user