The code at issue evolved as CT requirements changed. What started off as a
very simple conditional grew into a more complex if / else if block with
somewhat complicated logic and inline checks. As part of the fix, we
simplified the conditionals and refactored the inline checks to make use of
nice clear IsExternallyOperated() and IsGoogleOperated() functions. The end
result is a much more readable and clear set of logic that is easier to
test and we expanded test coverage. I think the big lesson for the
community is that it would have been better to have refactored earlier
rather the evolving the code to the point it became more complicated than
it needed to be.

On Thu, Aug 23, 2018 at 9:40 AM Ryan Sleevi <[email protected]> wrote:

>
>
> On Thu, Aug 23, 2018 at 8:50 AM, Andy Warner via dev-security-policy <
> [email protected]> wrote:
>>
>> * NOTE: The bug was due to an 'if/else' chain fall through. The code in
>> question has been refactored to be simpler and more readable.
>>
>
> Andy,
>
> It might be good for the community if you could describe the processes
> before and after the change, so that other CAs can help prevent similar
> issues with their own embedding systems.
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to