BouncyCastle dependency is out of date #168
Assignees
Labels
Comments
|
We are looking into this now, I'll keep you updated. |
timtay-microsoft
added a commit
that referenced
this issue
Dec 5, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 5, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 5, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 6, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 7, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 7, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 7, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 8, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 11, 2017
timtay-microsoft
added a commit
that referenced
this issue
Dec 11, 2017
|
Sorry for the delay on this issue, a lot of things got in the way. The fix for your issue is now checked in as of 165bec4 These changes will be in the next release. I'll notify you when that happens. |
prmathur-microsoft
added
fix checked in
|
It will take a day or two to propagate up to Maven central, but the latest release contains the fix for this issue: https://github.com/Azure/azure-iot-sdk-java/releases/tag/2018-1-23 I'm closing this issue for now, but feel free to re-open if this did not fix your issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The SDK lists
bcprov-jdk16as a dependency, which is significantly out of date.http://bouncy-castle.1462172.n4.nabble.com/Bouncycaslte-bcprov-jdk15-vs-bcprov-jdk16-td4656252.html
This causes conflicts with apps that are using a more modern version of bouncycastle. Please upgrade the SDK to use
bcprov-jdk15on.The text was updated successfully, but these errors were encountered: