Fix patches after "crypto: rollback BoringCrypto fips-20220613 update"
dagood opened this issue · comments
Once this goes into upstream:
We'll probably hit patch or test conflicts in microsoft/main and 1.22, 1.21, and 1.20. Essentially, we need to revert parts of:
Once the cherry-picks go through to the release branches, we should proactively merge to latest to get past the conflict, so the next release can go smoothly on each branch.
Quim says this is done