Remove dependency on ancient Bouncy Castle #359
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…valent from MITM module in order to remove legacy ProxyServer dependency on ancient version of Bouncy Castle.
jekh
force-pushed
the
remove-old-bouncycastle
branch
from
8b195c5 to
87199bf
Compare
jekh
added a commit
that referenced
this pull request
Jan 3, 2016
Remove dependency on ancient Bouncy Castle
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes browsermob-core's dependency on the ancient version of Bouncy Castle. This should also enable legacy proxy in standalone mode to work with HTTPS again.