Upgrade Tor to TRUE latest version (in Ubuntu)
Automated disclaimer: This post was written more than 15 years ago and I may not have looked at it since.
Older posts may not align with who I am today and how I would think or write, and may have been written in reaction to a cultural context that no longer applies. Some of my high school or college posts are just embarrassing. However, I have left them public because I believe in keeping old web pages aliveāand it's interesting to see how I've changed.
Very out of date (I don't know who is being irresponsible, but clearly someone is.)
Resources
Save & exit
gpg --export 94C09C7F. Enter trust, y, , quit.
Resources
To get the latest stable version, you'll have to add another repository to your sources.list
gpg --export 94C09C7F. Enter trust, y, , quit.
Save & exit
- Just use these instructions on the noreply.org repository
- Retrieve weasel's key and fingerprint over an insecure connection, so I suspect I'm okay. Better to provisionally trust the key than to not authenticate the package at all.
- Open the sources list file and set your trust level to ultimate, because the signed code will be running on your machine: gpg --fingerprint 94C09C7F
- Upgrade any packages you can: sudo apt-get upgrade
- Save & exit
Original instructions on the noreply.org/noreply/TheOnionRouter/TorOnDebian#Verifyingsignatureswithapt0.6.x">the one at noreply: gpg --keyserver subkeys.pgp.net --recv 94C09C7F. Enter trust, quit.
- Upgrade any packages you can: sudo gedit /etc/apt/sources.list file and set your trust level to ultimate, because the signed code will be running on your machine: gpg --keyserver subkeys.pgp.net --recv 94C09C7F | sudo apt-get update
- Verify that the key fingerprint matches Just use these instructions on the noreply.org repository, 2) trust the signer (weasel), and 3) update the tor package.
Add the following lines to your
sources.list
file and set your system to trust it.- Problem
- I discovered that I didn't have the latest stable version, you'll have to add another repository to your sources.list file and set your system to trust it.
- Problem
-
- Retrieve weasel's key and fingerprint over an insecure connection, so I suspect I'm okay. Better to provisionally trust the key than to not authenticate the package at all.
No comments yet.
Self-service commenting is not yet reimplemented after the Wordpress migration, sorry! For now, you can respond by email; please indicate whether you're OK with having your response posted publicly (and if so, under what name).