Repository navigation
Releases: OpenSourceKingdom/OSK.Security.Cryptography
Releases · OpenSourceKingdom/OSK.Security.Cryptography
Release list
2.1.1: Update Hexagonal Metadata (OSK-19) (#20)
Motivation ---- current metadata package is out of date Modifications ---- * Updated to latest convetions for meta data on ports Result ---- Better port documentation Fixes #19
2.1.0: Add better description and documentation handling (OSK-17) (#18)
Motivation ---- The current library doesn't have a decent README and the implementation doesn't provide a good way to see all currently added cryptographic key implementations to the dependency container Modifications ---- * Updated documentation * Added new CryptographicKeyDescriptor to help integrations describe an implementation via code * Updated packages for security fixes Result ---- library is better documented and has easier access to seeing integrations Fixes #17
2.0.1: Adjust CryptographicSigningAlgorithm (OSK-15) (#16)
Motivation ---- The CryptographicSigningAlgorithm is a class when it could be a struct Modifications ---- * Changed the type Result ---- THe CryptographicSigningAlgorithm is more appropriately a struct Fixes #15
2.0.0: Add better data signing handling (OSK-13) (#14)
Motivation ---- The library is heavily integrated with HashAlgorithmNames for signing algorithms, but this does not work for some AsymmetricKeyService's that do not use a classic signing hash algorithm Modifications ---- * [Breaking Change] - converted IAsymmetricKeyService to using new `CryptographicSigningAlgorithm` that can be extended by implementing Cryptography key service packages to special CryptographicSigningAlgorithms that they support Result ---- There is a more flexible way to separate supported signing algorithms from a hardset list of hash algorithms
1.2.0: Allow generic gets on CryptographicKeyServiceProvider (OSK-11) (#12)
* Allow generic gets on CryptographicKeyServiceProvider (OSK-11) Motivation ---- There is a limitation on the ICryptographicKeyServiceProvider that prevents getting a key service without knowing the typed key information. This makes the method unusable in some use cases. Modifications ---- * Updated dependency injection extensions to include a generic typed DI descriptor * Updated the ICryptographicKeyServiceProvider/CryptographicKeyServiceProvider to allow sending in generic key information * Added UnitTests Result ---- It is no longer required to know typed information to get a key service, as long as a key service has been registered on the DI that can handle the key information being requested * Project spacing * Avoid polluting the interface abstractions with unnecessary methods * Consistent modifier ordering
1.1.3: Add an extra interface for non-key specific key usage (OSK-9) (#10)
Motivation ---- Adding an extra interface for non-type usage, if desired Modifications ---- * Added new interface Result ---- Extra interface is now available for non-typed key service usage
1.1.2: Update extensions to add the key service provider (OSK-7) (#8)
Motivation ---- DI is not currently getting an instance for the ICryptographyKeyServiceProvider Modifications ---- * Add extension for this DI Result ---- Consumers will now be able to get a cryptography key service utilizing the new CryptographyKeyServiceProvider
1.1.1: Set key information to protected set (OSK-5) (#6)
* Set key information to protected set (OSK-5) Motivation ---- Unit tests can't access the key information for testing Modifications ---- * Make the key information a protected set so that implementations may set the value for unit testing Results ---- Unit testing can validate the key information * Combo that modifier access
1.1.0: Better type handling (OSK-3) (#4)
Motivation ---- There is a desire to perform better type handling with implementations of the cryptographic Abstractions. Modifications ---- * Adjusted abstractions to allow for better type handling on implementations * Updated core library to better handle typing Result ---- Library should now have better defined abstractions for type handling
1.0.0: Add initial project (OSK-1) (#2)
Motivation ---- Need an initial project for integrating cryptographic functions Modifications ---- * Added initial project * Added githu workflows Result ---- An initial project is now avialable