# 1.4.0.0 (16 November 2018)
- [#7](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/issues/7) - An exception about "The credentials supplied to the package were not recognized" [question]

# 1.3.0.0 (04 September 2018)
- [#2](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/pull/2) - Split functionality into two packages contributed by [StefH](https://github.com/StefH)
- [#5](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/pull/5) - Added support for decoding OpenSSL RSA public keys in PEM format. contributed by [LamarLugli](https://github.com/LamarLugli)
- [#8](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/pull/8) - Use archive.org link for "Based on" contributed by [nelsonjchen](https://github.com/nelsonjchen)
- [#10](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/pull/10) - OpenSSL PEM (useKeyContainer) contributed by [StefH](https://github.com/StefH)
- [#3](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/issues/3) - InvalidCastException on constructor
- [#4](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/issues/4) - OpenSSLPrivateKeyDecoder.Decode fails on .Net Core on Linux [bug]
- [#6](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/issues/6) - Sign Assembly [feature]
- [#9](https://github.com/StefH/OpenSSL-X509Certificate2-Provider/issues/9) - Best practice for using provider to load OpenSSL PEM files for HttpWebRequest client certificate authentication?