Repository navigation
Would BC C# accept O‘zMSt test profiles and explicit parameter APIs? #749
fubaydullaev
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have a local .NET prototype for the O‘zMSt 285 Annex C digest, explicit substitution tables for O‘zMSt 270 and 285, and O‘zMSt 286 signing and verification with the Annex B test curve. It reuses BC’s GOST primitives. All 11 targeted tests passed on .NET 6 against the patched 8e709eb base. The Annex B signature scalars also verified across C#, Java and an OpenSSL provider.
The proposed scope is test vectors and caller supplied parameters. Production OID assignments and PKI encodings need authoritative references. The supplied signature document carries an older edition label internally, so the tests identify the annex they exercise.
Would you prefer a first PR limited to the digest and its tests? Are there API conventions you would like the .NET implementation to follow?
All reactions