Custom Query (26254 matches)
Results (31 - 33 of 26254)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3308 | implemented | Fingerprint for 886DDD89 key on web page | ||
| Description |
While the signing keys for most of the distributions are found at: https://www.torproject.org/docs/verifying-signatures.html.en The fingerprint for the 886DDD89 (deb.torproject.org archive signing key) is not found there. Which it probably should be. Neither is it shown on the debian install page, except hidden away in the command: gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add - I would recommend adding the fingerprint and a short note on how to check it to both places. |
|||
| #4039 | fixed | MAT patches (multiselect bug, etc.) | ||
| Description |
I've made a few bug fixes/cleanups to the Metadata Anonymisation Toolkit source. Find them here: git://github.com/4ZM/Metadata-Anonymisation-Toolkit.git Feel free to bring them upstream. |
|||
| #4089 | not a bug | Listening to wrong IP according to log (due to nic alias?) | ||
| Description |
The log reads: "Now checking whether ORPort A.B.172.47:9001 and DirPort A.B.172.47:9030 are reachable..." But the torrc has: ORListenAddress A.B.172.50 DirListenAddress A.B.172.50 After tor start it really does listen to A.B.172.50 and not to the ip from the log. The probable cause for this is the use of a physical eth0 with ip A.B.172.47 and an alias eth0:1 with A.B.172.50. Running on Gentoo. |
|||
