Ah, thanks! I was trying to figure out the context if it was a bug or intentional - sounds like the former, in which case, all is well :)
On Fri, Jun 1, 2018 at 3:17 PM, J.C. Jones via dev-security-policy < [email protected]> wrote: > Ryan - > > Originally the Observatory had "Subject+SPKI" hash field. Someone filed a > bug that Subject+SPKI field wasn't as useful for external comparisons as > the SPKI, and the Observatory changed over, replacing the old Subject+SPKI > hash with a pure SPKI hash. > > We were proposing to switch to just the SPKI, simply because that is what > the Observatory is using today. However, there's no reason not to have the > Observatory provide the Subject+SPKI hash alongside the SPKI, and then we > can keep that field and effectively add the SPKI hash. That seems like a > good idea, for all the reasons David pointed out in 2016 > <https://github.com/mozilla/tls-observatory/issues/144>. > > Thanks for catching this! > > Cheers, > J.C. > > On Fri, Jun 1, 2018 at 11:57 AM, Julien Vehent via dev-security-policy < > [email protected]> wrote: > > > I think the revert was a mistake. I should have added the SPKI instead of > > replacing the Subject+SPKI with SPKI. (I don't recall the discussion at > the > > time, but I think someone confused Subject+SPKI for SPKI and I meant to > > address the confusion). > > > > I'll re-add the subject+spki field, this time in addition to SPKI, and > > re-populate the DB. > > > > - Julien > > _______________________________________________ > > dev-security-policy mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-security-policy > > > _______________________________________________ > dev-security-policy mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-security-policy > _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
