You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Valid RSA-384 signatures are sometimes reported as invalid on Android #118366
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1113280 Error message validated:[System.Security.Cryptography.Rsa.Tests.SignVerify.VerifySignature_SHA1_384] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 8/14/2025 3:47:19 PM UTC
I was not able to reproduce this issue on emulator locally (API 25, 29, 33) but I could reproduce the test failure when running on a physical Samsung device (API 35). When I switch from Release to Debug, the test run crashes with the following failed assertion:
D DOTNET : ((null) warning) Process terminated. Assertion failed.
D DOTNET : ((null) warning) RsaVerificationPrimitive returned 47 when 48 was expected
D DOTNET : at System.Diagnostics.DebugProvider.Fail(String message, String detailMessage)
D DOTNET : at System.Diagnostics.Debug.Fail(String message, String detailMessage)
D DOTNET : at System.Diagnostics.Debug.Assert(Boolean condition, String message, String detailMessage)
D DOTNET : at System.Diagnostics.Debug.Assert(Boolean condition, String message)
D DOTNET : at System.Diagnostics.Debug.Assert(Boolean condition, AssertInterpolatedStringHandler& message)
D DOTNET : at System.Security.Cryptography.RSAImplementation.RSAAndroid.VerifyHash(ReadOnlySpan`1 hash, ReadOnlySpan`1 signature, HashAlgorithmName hashAlgorithm, RSASignaturePadding padding)
D DOTNET : at System.Security.Cryptography.RSA.VerifyData(ReadOnlySpan`1 data, ReadOnlySpan`1 signature, HashAlgorithmName hashAlgorithm, RSASignaturePadding padding)
D DOTNET : at System.Security.Cryptography.Rsa.Tests.SignVerify_Span.VerifyData(RSA rsa, Byte[] data, Byte[] signature, HashAlgorithmName hashAlgorithm, RSASignaturePadding padding)
D DOTNET : at Sy
Activity
dotnet-policy-service commentedon Aug 4, 2025
Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.
bartonjs commentedon Aug 4, 2025
Log exerpts:
It doesn't seem to happen on every Android run, so maybe one of the machines is on a new OS version than the rest?
dotnet-policy-service commentedon Aug 4, 2025
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
BrzVlad commentedon Aug 11, 2025
Reproduces on my local device
vitek-karas commentedon Aug 13, 2025
We'll investigate and see if this needs a fix in RC2.
simonrozsival commentedon Aug 18, 2025
I was not able to reproduce this issue on emulator locally (API 25, 29, 33) but I could reproduce the test failure when running on a physical Samsung device (API 35). When I switch from Release to Debug, the test run crashes with the following failed assertion:
vcsjones commentedon Aug 18, 2025
I can take a look sometime this week.
simonrozsival commentedon Aug 19, 2025
@vcsjones I think I figured it out. Please feel free to suggest an alternative fix to #118880 if there is a better way to address this issue.