ebourg / jsign / #352

81%

push

Make `PrivateKeyUtils#load` method file extension agnostic

As outlined in #264, this is achieved by trying to parse the key file
according to one of the supported formats in sequence until one works.
Given that there are only two supported formats at the moment, and that
PEM files are attempted first and more common in the wild than PVK, this
approach should have good enough performance. Because a Java exception
can only have a single cause, I've attached the underlying parse
exceptions to the higher-level `KeyException` as supressed exceptions.
These get displayed to consumers on e.g. stacktraces, allowing them to
know what exactly went wrong when parsing either format.

While at it, I've added a test to ensure that this extension-agnostic
behavior is maintained over time.

Resolves #264.

9 of 9 new or added lines in 1 file covered. (100.0%)

4722 of 5662 relevant lines covered (83.4%)

0.83 hits per line