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

Order of package-installation prevents new versions of tor from being installed #5

Open
reformat0r opened this issue Apr 22, 2021 · 1 comment

Comments

@reformat0r
Copy link

reformat0r commented Apr 22, 2021

I noticed that when building the image using the latest Dockerfile, an outdated version of tor is being installed.
The reason seems to be that the signing keys are expired:

The following signatures were invalid: EXPKEYSIG 74A941BA219EC810 deb.torproject.org archive signing key

I think the issue lies with the fact that deb.torproject.org-keyring and tor are being installed in the same transaction, meaning that when apt checks which version of tor to install, the keys are not yet updated.

tor-server/Dockerfile

Lines 38 to 43 in 2a9ed8e

&& apt-get install --no-install-recommends --no-install-suggests -y \
pwgen \
iputils-ping \
tor \
tor-geoipdb \
deb.torproject.org-keyring \

I resolved the issue by first executing apt-get install deb.torproject.org-keyring on its own, before installing tor:

 # Install tor with GeoIP and obfs4proxy & backup torrc \
 && apt-get update \
 && apt-get install deb.torproject.org-keyring -y \
 && apt-get install --no-install-recommends --no-install-suggests -y \
        pwgen \
        iputils-ping \
        tor \
        tor-geoipdb
@andrewbpowers
Copy link

Great work!

How to you install the "tor-server" or build the image after this changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants