Nelson B wrote: > beltzner wrote: >> On 2/1/07, Gervase Markham <[EMAIL PROTECTED]> wrote: >>> Not to my knowledge. Such a thing would be fantastic! >> What I was able to offer the W3C was: >> >> http://www.w3.org/2006/WSC/wiki/NoteMozillaCertificateValidationErrors >> >> But if someone could help me construct the workflow, that would be >> great. Any takers? > > The page above cites 6 things that can be wrong in a cert chain. > There are many MANY more than 6. A full flow chart would be Quite > large. So I'm curious to know what level of detail you want.
I think we could start from the states that are visible to the user: - works - silent rejection of connection (is this even possible?) - all different error dialogs, prompts or similar that get shown to user Then, I'd give a high level, short description of the checks that can lead to each of the different dialogs. That way all the checks would be lumped to something like half a dozen (?) boxes in the flowchart. -- Heikki Toivonen _______________________________________________ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security
