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

New Tor Browser signing subkey #260

Closed
epidemics-scepticism opened this issue Jan 25, 2017 · 5 comments
Closed

New Tor Browser signing subkey #260

epidemics-scepticism opened this issue Jan 25, 2017 · 5 comments

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@epidemics-scepticism
Copy link

@epidemics-scepticism epidemics-scepticism commented Jan 25, 2017

D1483FA6C3C07136 is the new signing subkey for the 6.5 Tor Browser release, this subkey isn't in the hardcoded keys distributed with torbrowser-launcher.

@zkutch
Copy link

@zkutch zkutch commented Jan 25, 2017

I posted this question to #tor and https://tor.stackexchange.com/questions/13814/upgrading-to-6-5 against not upgrading on debian wheezy.
Is there some way other to waiting debian maintaineer , for example suspend/not upgrade to 6.5? Such problems will be in future also.

@zkutch
Copy link

@zkutch zkutch commented Jan 25, 2017

Solution for debian wheezy found following:
update/refresh keys from mit using command
gpg --keyserver pgp.mit.edu --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys
after this torbrowser-launcher upgrades itself successfully

@epidemics-scepticism
Copy link
Author

@epidemics-scepticism epidemics-scepticism commented Jan 25, 2017

Temporary workaround: gpg --homedir "$HOME/.local/share/torbrowser/gnupg_homedir/" --refresh-keys --keyserver pgp.mit.edu

@micahflee
Copy link
Owner

@micahflee micahflee commented Jan 27, 2017

Awesome, thanks @epidemics-scepticism @zkutch for troubleshooting

@geor-g
Copy link

@geor-g geor-g commented Jan 29, 2017

See #263 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment