here is a quick and dirty hack i have used in torbirdy 1.4 to make the removal of the http-proxy persistent. so far, it has worked without issue and don’t foresee why it would cause any problems. absent any hiccups, i’ll likely take screenshots and add it to the guide i work on, as it makes key management in icedove significantly easier.
- install torbirdy as you usually would and close icedove
- open terminal
- type “cd .icedove/[your profile name]/extensions”
- type “7z x castironthunderbirdclub@torproject.org.xpi components”
- type “nano components/torbirdy.js”
- find the following code, starting at line 216:
"–display-charset utf-8 " +
// We want to ensure that Enigmail is proxy aware even when it runs gpg in a shell
"–keyserver-options http-proxy=http://127.0.0.1:8118 ",
modify line 216 to replace the trailing “+” with a “,” and add “//” before the text in line 218 to comment it out.it should look like the code below (changes are in bold):
"–display-charset utf-8 ",
// We want to ensure that Enigmail is proxy aware even when it runs gpg in a shell
// "–keyserver-options http-proxy=http://127.0.0.1:8118 ",
- save the file and exit out of nano (or whatever editor you use)
- type “7z u castironthunderbirdclub@torproject.org.xpi *”
- type “rm -rf components”
from now on, every time you start icedove, you will not have to manually edit the “advanced options” in enigmail to communicate with a keyserver from inside icedove.