{"push_id":2489393486,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e28552dec814351e4583220a445f311b816c01e8","before":"c9775322408095b42840c5599942bbe9a74f7921","commits":[{"sha":"e28552dec814351e4583220a445f311b816c01e8","author":{"name":"David Benjamin","email":"348b1b6801801c3d890b2e1589a8e36441d09fdc@google.com"},"message":"Add an API to disable RSA-PSS for certificates.\n\nChrome uses the platform certificate verifier and thus cannot reliably\nexpect PSS signatures to work in all configurations. Add an API for the\nconsumer to inform BoringSSL of this ability. We will then adjust our\nadvertisements accordingly.\n\nNote that, because TLS 1.2 does not have the signature_algorithms_cert\nextension, turning off TLS 1.3 and using this API will stop advertising\nRSA-PSS. I believe this is the correct behavior given the semantics of\nthat code point.\n\nThe tests check the various combinations here, as well as checking that\nthe peer never sends signature_algorithms_cert identical to\nsignature_algorithms.\n\nBug: 229\nChange-Id: I8c33a93efdc9252097e3899425b49548fc42a93a\nReviewed-on: https://boringssl-review.googlesource.com/27488\nCommit-Queue: David Benjamin <davidben@google.com>\nCQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>\nReviewed-by: Steven Valdez <svaldez@google.com>","distinct":true,"url":"https://api.github.com/repos/google/boringssl/commits/e28552dec814351e4583220a445f311b816c01e8"}]}
{"actor":{"display_login":"agl"}}