Add support for ГОСТ Р 34.10 digital signatures
- Implemented the GostKeyValue class for handling public key parameters in ГОСТ Р 34.10 digital signatures. - Created the GostSignedXml class to manage XML signatures using ГОСТ 34.10, including methods for computing and checking signatures. - Developed the GostSignedXmlImpl class to encapsulate the signature computation logic and public key retrieval. - Added specific key value classes for ГОСТ Р 34.10-2001, ГОСТ Р 34.10-2012/256, and ГОСТ Р 34.10-2012/512 to support different signature algorithms. - Ensured compatibility with existing XML signature standards while integrating ГОСТ cryptography.
This commit is contained in:
@@ -61,9 +61,12 @@ The script spins up MongoDB/Redis via Testcontainers and requires:
|
||||
|
||||
Multiple suites (Concelier connectors, Excititor worker/WebService, Scheduler)
|
||||
fall back to [Mongo2Go](https://github.com/Mongo2Go/Mongo2Go) when a developer
|
||||
does not have a local `mongod` listening on `127.0.0.1:27017`. Modern distros
|
||||
ship OpenSSL 3 by default, so you **must** expose the legacy OpenSSL 1.1
|
||||
libraries that the embedded `mongod` requires:
|
||||
does not have a local `mongod` listening on `127.0.0.1:27017`. **This is a
|
||||
test-only dependency**: production/dev runtime MongoDB always runs inside the
|
||||
compose/k8s network using the standard StellaOps cryptography stack. Modern
|
||||
distros ship OpenSSL 3 by default, so when Mongo2Go starts its embedded
|
||||
`mongod` you **must** expose the legacy OpenSSL 1.1 libraries that binary
|
||||
expects:
|
||||
|
||||
1. From the repo root, export the provided binaries before running any tests:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user