Skip to content
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

update geoip #60

Closed
n8fr8 opened this issue Nov 5, 2016 · 1 comment
Closed

update geoip #60

n8fr8 opened this issue Nov 5, 2016 · 1 comment

Comments

@n8fr8
Copy link
Member

n8fr8 commented Nov 5, 2016

I use both orbot on my phone and torbrowser on pc. There is an interesting bug about the geoip file.I have to use some bridges to make tor work well because i am in China.I found that the geoip file in torbrowser is the latest version but it is the old in orbot. So some bridges are not in the excluding states according to torbrowser but they are excluded in orbot. In order to resolve the problem,i replace the geoip file of orbot in the directory /date/date/org.torproject.android/app_bin with the latest geoip in torbrowser. Then something new happened. When i use some bridges that are not excluded in both old and latest version geoip file, it is shown in orbot log file something like that Received http status code 404("Not found") from server 'xxx.xxx.xxx.xxx:xxxx' while fetching "tor/keys/fp-sk/xxxxxxxxxxxxxxxxxxxx......).But the bridges work well with the old geoip file. The bug if found in the newest version of orbot from 15.2.0-RC2 to 15.2.0-RC7-multi. I hope that the developers can fix the bug and use the latest geoip file with every new version orbot.

@n8fr8 n8fr8 added this to the Developer Issues milestone Apr 27, 2018
@bitmold
Copy link
Collaborator

bitmold commented Nov 29, 2020

Closing this since the tor-android-binary should contain the updates needed

@bitmold bitmold closed this as completed Nov 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants