bz/bordercastle
bz/bordercastle
1
0
Fork 0
Code Issues Pull requests Releases 1 Wiki Activity

polishing

Browse source
This commit is contained in:
Leon Poyyayil 2025-10-24 08:54:45 +02:00
parent 46fd654f46
commit 6178c58132
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -18,18 +18,18 @@ First of all, SpongyCastle doesn't appear to be maintained any longer and thus i
More importantly, as a manufacturer of software libraries and components, it turned out to be important to allow flexible combination of our libraries with other components, while not enforcing dependency version restrictions on the users of our libraries. More importantly, as a manufacturer of software libraries and components, it turned out to be important to allow flexible combination of our libraries with other components, while not enforcing dependency version restrictions on the users of our libraries.
Hence, an application making use of our library could still make use any version of SpongyCastle or BouncyCastle without running into class loader problems, while still guaranteeing the tested and well-defined environment of our BorderCastle version. Hence, an application making use of our library could still make use of any version of SpongyCastle or BouncyCastle without running into class loader problems, while still guaranteeing the tested and well-defined environment of our BorderCastle version.
Of course, a lot of code duplication could be avoided by using the BorderCastle classes - simply by renaming the imported packages. Of course, a lot of code duplication could be avoided by using the BorderCastle classes everywhere - simply by renaming the imported packages.
## Changes from BouncyCastle ## Changes in respect to BouncyCastle
- to avoid class loader conflicts, all packages have been renamed from `org.bouncycastle.*` to `org.bordercastle.*` - to avoid class loader conflicts, all packages have been renamed from `org.bouncycastle.*` to `org.bordercastle.*`
- the Java Security API provider name is "**BoCa**" rather than "**BC**" (resp. "**BoCaPQC**" instead of "**BCPQC**" for the post quantum provider) - the Java Security API provider name is "**BoCa**" rather than "**BC**" (resp. "**BoCaPQC**" instead of "**BCPQC**" for the post quantum provider)
- no class name changes, so the `BouncyCastleProvider` class remains **Bouncy**, not **Border**, but moves to the `org.bordercastle.jce.provider` package - no class name changes, so the `BouncyCastleProvider` class remains **Bouncy**, not **Border**, but moves to the `org.bordercastle.jce.provider` package
- added a simple class to allow for version checking without having to instantiate a provider (which is an expensive operation): `org.bordercastle.Version` - added a simple class to allow for version checking without having to instantiate a provider (which is an expensive operation): `org.bordercastle.Version`
- changed the names of the libraries to have a consistent naming pattern - changed the names of the resulting built library files to have a consistent naming pattern
- added new constructors for the provider classes to allow instantiating multiple ones with different names, so they can be used in parallel - added new constructors for the provider classes to allow instantiating multiple ones with different names, so they can be used in parallel when needed
## Current version ## Current version