Conversation
…21), most recent Tor.framework release without code change
bitmold
requested review from
adrastaea,
holmesworcester,
islathehut,
kingalg and
mcginty
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Was having difficulty testing the iOS app on the nearly 6 year old version of Tor included in the app. It supported v2 onion services. The logs would be flooded with warnings saying this Tor is old and that it'd have a harder and harder time forming circuits over the tor network.
@kingalg had some problems with Tor 0.4.8.21 when that was included in the big PR. This updates to the newer 0.4.9 series and the changes can be tested in isolation on this branch.