Skip to content

[microsoft/dev.boringcrypto.go1.16] Rearrange FIPS patches, start at 0100#513

Merged
dagood merged 1 commit into
microsoft:microsoft/dev.boringcrypto.go1.16from
dagood:dev/dagood/better-patches-b1.16
Mar 31, 2022
Merged

[microsoft/dev.boringcrypto.go1.16] Rearrange FIPS patches, start at 0100#513
dagood merged 1 commit into
microsoft:microsoft/dev.boringcrypto.go1.16from
dagood:dev/dagood/better-patches-b1.16

Conversation

@dagood
Copy link
Copy Markdown
Member

@dagood dagood commented Mar 31, 2022

This starts with the same set of FIPS patch layering improvements as:

Then adds in a renumbering command so the infra (1.16) patches start at 0001 and FIPS patches start at 0100.

I ran the same check as I did there: diff before and after shows zero changes.

Make adding crypto/internal/backend and importing the OpenSSL library happen in the same patch.

Put repo-spanning boring -> OpenSSL changes in its own patch.

Put the vendoring patch after the patch that adds the OpenSSL dependency, for simpler regeneration.

Bring test adjustments/fixes together into the final patch.
@dagood
Copy link
Copy Markdown
Member Author

dagood commented Mar 31, 2022

After the renumbering, you need this git-go-patch update to be able to round-trip the patch files:

@dagood dagood requested review from chsienki and jaredpar March 31, 2022 18:28
@dagood dagood merged commit f88ef9a into microsoft:microsoft/dev.boringcrypto.go1.16 Mar 31, 2022
@dagood dagood deleted the dev/dagood/better-patches-b1.16 branch March 31, 2022 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants