{"push_id":654429570,"size":2,"distinct_size":2,"ref":"refs/heads/zi/refactor-sha1-deprecation","head":"a272f06e51df3ff2bb02102ea2adfa8ac9a75c65","before":"2b4130367a2ed8de7caa5f6c3676f8c0915043c7","commits":[{"sha":"7ece1a09ebe59a29374c9396ef915df1541ddd09","author":{"email":"1396bc8a5619af2d9f66a3d7b7abd12a471a957c@cloudflare.com","name":"Zi Lin"},"message":"Add a dynamic bundle ubiquity test of prioritizing SHA-2 intermediate","distinct":true,"url":"https://api.github.com/repos/cloudflare/cfssl/commits/7ece1a09ebe59a29374c9396ef915df1541ddd09"},{"sha":"a272f06e51df3ff2bb02102ea2adfa8ac9a75c65","author":{"email":"1396bc8a5619af2d9f66a3d7b7abd12a471a957c@cloudflare.com","name":"Zi Lin"},"message":"Rewrite/refactor SHA1 deprecation logic and improve test coverage.\n\n- Revert the initial design of SHA1 deprecation policy being part of\n  platform metadata because it makes metadata bloated. Instead, the\n  platform metadata should only contain info on CA trust root stores\n  and crypto support.\n- Add a new type called SHA1Deprecated to handle SHA1\n  deprecation warning.\n- Add support to Firefox SHA1 deprecation policy in SHA1Deprecated.\n- Make it explicit that ubiquity scoring doesn't take SHA1\n  deprecation into account. Right now the weights of Chrome browsers\n  in the metadata file is encoded as 0. So this is a safe change.\n- Hardcode the list of platforms that would conditionally reject\n  SHA1 certificate chain.\n- Increase test coverage of package ubiquity","distinct":true,"url":"https://api.github.com/repos/cloudflare/cfssl/commits/a272f06e51df3ff2bb02102ea2adfa8ac9a75c65"}]}