Skip to content

Conversation

@jonathanpeppers
Copy link
Member

This adds [Obsolete] (with error:true) to:

  • PackageNamingPolicy.LowercaseHash
  • PackageNamingPolicy.LowercaseMD5

If these values are encountered at runtime a NotSupportedException
will be thrown.

Most of the remaining changes were updates to tests. Upstream in
xamarin/xamarin-android, we will likely need to emit a new build error
with an error code.

Other changes:

  • I removed a place BaseGeneratorTest.cs was using MD5.Create().
  • This exposed a place we need to reset the initial state of Crc64
    when an instance is reused for hashing.

@jonpryor
Copy link
Contributor

Fixes: dotnet/android#3844

Fixes: dotnet/android#3844

This adds `[Obsolete]` (with `error:true`) to:

* `PackageNamingPolicy.LowercaseHash`
* `PackageNamingPolicy.LowercaseMD5`

If these values are encountered at runtime a `NotSupportedException`
will be thrown.

Most of the remaining changes were updates to tests. Upstream in
xamarin/xamarin-android, we will likely need to emit a new build error
with an error code.

Other changes:

* I removed a place `BaseGeneratorTest.cs` was using `MD5.Create()`.
* This exposed a place we need to reset the initial state of `Crc64`
  when an instance is reused for hashing.
@jonpryor jonpryor merged commit baf43b0 into dotnet:master Oct 28, 2019
jonpryor pushed a commit that referenced this pull request Nov 8, 2019
Context: dotnet/android#3844

Context: dotnet/android@88a1d6c

Entirely remove support for MD5 output, so that we can reliably use
Xamarin.Android on machines with FIPS enalbed.

This adds `[Obsolete (..., error:true)]` to:

  * `PackageNamingPolicy.LowercaseHash`
  * `PackageNamingPolicy.LowercaseMD5`

If these values are encountered at runtime a `NotSupportedException`
will be thrown.

Most of the remaining changes were updates to tests.  Upstream in
xamarin/xamarin-android, we will likely need to emit a new build
error with an error code.

Other changes:

  * I removed a place `BaseGeneratorTest.cs` was using `MD5.Create()`.
  * This exposed a place we need to reset the initial state of `Crc64`
    when an instance is reused for hashing.
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants