-
Notifications
You must be signed in to change notification settings - Fork 998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BouncyCastle update to > 1.68 #1881
Comments
@nils-ohlmeier: It has been fixed by #1884? |
The current version of bouncycastle is 1.75 |
@bgrozev: Thanks for your message, it is possible to update to 1.76? All current Bouncy Castle 1.75 version repositories and do not forget others which old: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We attempted an update from BouncyCastle 1.68 to version 1.70, but had to revert back to 1.68 because of a new issue in BouncyCastle >= 1.69, which prevents the media path between the JVB and Jigasi getting established (see #1878 for details).
We created an issue on the BouncyCastle end bcgit/bc-java#1159 to get this resolved.
This ticket is mostly for keeping track of this blocker and update once the issue is fixed on the BouncyCastle side.
Note: a possible alternative is that once Jitsi Desktop is updated to support DTLS 1.2 and is used/available for Jigasi we could probably switch to a recent version of BouncyCastle as well, as the issue above only affects DTLS 1.0 clients.
The text was updated successfully, but these errors were encountered: