most (>57% cwfr) of the tor network still vulnerable to CVE-2016-8860 - update your relay!
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays https://blog.torproject.org/blog/tor-0289-released-important-fixes Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12). It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way). Update instructions Debian/Ubuntu ============== make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en (you can also use the debian repository but the Torproject's repo will provide you with the latest releases) aptitude update && aptitude install tor CentOS/RHEL/Fedora =================== yum install --enablerepo=epel-testing tor FreeBSD ============ pkg update pkg upgrade OpenBSD =========== pkg_add -u tor Windows ======== No updated binaries available for this platform yet. [1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
On Tue, Oct 25, 2016 at 09:48:00PM +0000, nusenu wrote:
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number.
In the case of OpenBSD, MTier published a binary package (patch) only yesterday. I had reported them to update on 2016-10-19 to use a patch from openbsd-ports@ mailing list (net/tor port maintainer). Consequently, OpenBSD 6.0's -stable has tor-0.2.7.6p1 (vulnerable) and MTier's binary packages have tor-0.2.7.6p2 (not vulnerable). -snapshots has tor-0.2.8.9.
32 relays updated (Debian + Tor compiled to latest version) I am getting too old for this without a server management system .... Markus 2016-10-25 23:48 GMT+02:00 nusenu <nusenu@openmailbox.org>:
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays
https://blog.torproject.org/blog/tor-0289-released-important-fixes
Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12).
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way).
Update instructions
Debian/Ubuntu ==============
make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en
(you can also use the debian repository but the Torproject's repo will provide you with the latest releases)
aptitude update && aptitude install tor
CentOS/RHEL/Fedora ===================
yum install --enablerepo=epel-testing tor
FreeBSD ============
pkg update pkg upgrade
OpenBSD ===========
pkg_add -u tor
Windows ========
No updated binaries available for this platform yet.
[1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched
optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I feel you Markus, I did 24. I wrote a bash script to update/upgrade/reboot.
On Oct 26, 2016, at 02:17, Markus Koch <niftybunny@googlemail.com> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
Markus
2016-10-25 23:48 GMT+02:00 nusenu <nusenu@openmailbox.org>:
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays
https://blog.torproject.org/blog/tor-0289-released-important-fixes
Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12).
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way).
Update instructions
Debian/Ubuntu ==============
make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en
(you can also use the debian repository but the Torproject's repo will provide you with the latest releases)
aptitude update && aptitude install tor
CentOS/RHEL/Fedora ===================
yum install --enablerepo=epel-testing tor
FreeBSD ============
pkg update pkg upgrade
OpenBSD ===========
pkg_add -u tor
Windows ========
No updated binaries available for this platform yet.
[1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched
optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I did it like a real man, just me hands and putty without any bash scripts and these modern devil tools! markus Sent from my iPad
On 26 Oct 2016, at 09:18, John Ricketts <john@quintex.com> wrote:
I feel you Markus, I did 24. I wrote a bash script to update/upgrade/reboot.
On Oct 26, 2016, at 02:17, Markus Koch <niftybunny@googlemail.com> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
Markus
2016-10-25 23:48 GMT+02:00 nusenu <nusenu@openmailbox.org>:
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays
https://blog.torproject.org/blog/tor-0289-released-important-fixes
Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12).
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way).
Update instructions
Debian/Ubuntu ==============
make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en
(you can also use the debian repository but the Torproject's repo will provide you with the latest releases)
aptitude update && aptitude install tor
CentOS/RHEL/Fedora ===================
yum install --enablerepo=epel-testing tor
FreeBSD ============
pkg update pkg upgrade
OpenBSD ===========
pkg_add -u tor
Windows ========
No updated binaries available for this platform yet.
[1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched
optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Haha ok! Nice hard work so ;) Good luck for next update ! (hope it will be ok for a long time!) Le 26/10/2016 à 09:30, Markus Koch a écrit :
I did it like a real man, just me hands and putty without any bash scripts and these modern devil tools!
markus
Sent from my iPad
On 26 Oct 2016, at 09:18, John Ricketts <john@quintex.com> wrote:
I feel you Markus, I did 24. I wrote a bash script to update/upgrade/reboot.
On Oct 26, 2016, at 02:17, Markus Koch <niftybunny@googlemail.com> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
Markus
2016-10-25 23:48 GMT+02:00 nusenu <nusenu@openmailbox.org>:
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays
https://blog.torproject.org/blog/tor-0289-released-important-fixes
Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12).
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way).
Update instructions
Debian/Ubuntu ==============
make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en
(you can also use the debian repository but the Torproject's repo will provide you with the latest releases)
aptitude update && aptitude install tor
CentOS/RHEL/Fedora ===================
yum install --enablerepo=epel-testing tor
FreeBSD ============
pkg update pkg upgrade
OpenBSD ===========
pkg_add -u tor
Windows ========
No updated binaries available for this platform yet.
[1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched
optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Petrusko EBE23AE5
Markus, I'm too damn old to type that accurately, My hands shake from old mechanical keyboards and my eyes are irradiated from old Wyse 50 terminals...
On Oct 26, 2016, at 02:31, Markus Koch <niftybunny@googlemail.com> wrote:
I did it like a real man, just me hands and putty without any bash scripts and these modern devil tools!
markus
Sent from my iPad
On 26 Oct 2016, at 09:18, John Ricketts <john@quintex.com> wrote:
I feel you Markus, I did 24. I wrote a bash script to update/upgrade/reboot.
On Oct 26, 2016, at 02:17, Markus Koch <niftybunny@googlemail.com> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
Markus
2016-10-25 23:48 GMT+02:00 nusenu <nusenu@openmailbox.org>:
just a reminder since most of the tor network (including some of the biggest operators) still runs vulnerable relays
https://blog.torproject.org/blog/tor-0289-released-important-fixes
Since 2/3 directory authorities removed most vulnerable versions from their 'recommended versions' you should see a log entry if you run outdated versions (except if you run 0.2.5.12).
It is not possible to reliable determine the exact CW fraction affected[1] due to the fact that patches were released that didn't increase tor's version number. Therefore it is also possible that you get log entries even if you run a patched version (IMHO this hasn't been handled in the most professional way).
Update instructions
Debian/Ubuntu ==============
make sure you use the Torproject repository: https://www.torproject.org/docs/debian.html.en
(you can also use the debian repository but the Torproject's repo will provide you with the latest releases)
aptitude update && aptitude install tor
CentOS/RHEL/Fedora ===================
yum install --enablerepo=epel-testing tor
FreeBSD ============
pkg update pkg upgrade
OpenBSD ===========
pkg_add -u tor
Windows ========
No updated binaries available for this platform yet.
[1] as of 2016-10-25 18:00 (onionoo data) conservative estimate ---------------------- (counts only 0.2.8.9 and 0.2.9.4-alpha as patched) 31% CW fraction patched
optimistic estimate ------------------- (additionally assumes every non-Windows running 0.2.4.27, 0.2.5.12, 0.2.6.10, 0.2.7.6 that restarted since 2016-10-17 is patched): 43% CW fraction patched
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package? (only found 28 relays) +---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
niftyeuropeanbunny -> bridges, a lot of them Markus Sent from my iPad On 26 Oct 2016, at 10:22, nusenu <nusenu@openmailbox.org> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package?
(only found 28 relays)
+---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I was talking about the bridges you can see on the screen shot. These were my "backup" Digital Ocean accounts because Digital Ocean kicked my exits after 2-3 months. Digital Ocean is not allowing any exits anymore so I use the prepaid accounts to run bridges. The bridges will all die end of the year. I will just run them until the prepaid money is gone. The three exists currently running with Digital Ocean are also dead in the water. Just waiting for the next abuse mail so they get kicked. Trying and testing new exits for a world without Digital Ocean. Markus 2016-10-26 10:22 GMT+02:00 nusenu <nusenu@openmailbox.org>:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package?
(only found 28 relays)
+---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Wed, 26 Oct 2016 10:53:19 +0200 Markus Koch <niftybunny@googlemail.com> wrote:
I was talking about the bridges you can see on the screen shot. These were my "backup" Digital Ocean accounts because Digital Ocean kicked my exits after 2-3 months. Digital Ocean is not allowing any exits anymore so I use the prepaid accounts to run bridges. The bridges will all die end of the year. I will just run them until the prepaid money is gone.
Bridges consume next to no bandwidth and can be run on any low speed or b/w limited connections, whereas you'd get much better use from the resources you currently get at DO by running regular non-exit relays there. -- With respect, Roman
Hi, I'm very interested in setting up unattended upgrades for tor. I tried searching for instructions on how to do it. But the only instructions I could really find didn't work (on the Library Freedom git project). How do I write the config so that the tor repo (or whatever it's called) is updated by unattended upgrades? Thanks. On Oct 26, 2016 1:23 AM, "nusenu" <nusenu@openmailbox.org> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package? (only found 28 relays) +---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 1 Nov. 2016, at 16:44, Greg <greggth@gmail.com> wrote:
Hi, I'm very interested in setting up unattended upgrades for tor. I tried searching for instructions on how to do it. But the only instructions I could really find didn't work (on the Library Freedom git project). How do I write the config so that the tor repo (or whatever it's called) is updated by unattended upgrades?
If you are using Debian or Ubuntu (or apt): 1. Modify your sources.list to include the tor repository https://www.torproject.org/docs/debian.html.en 2. Modify Debian: Unattended-Upgrade::Origins-Pattern Ubuntu: Unattended-Upgrade::Allowed-Origins to include the packages you want updated: $EDITOR /etc/apt/apt.conf.d/50unattended-upgrades Tim
Thanks.
On Oct 26, 2016 1:23 AM, "nusenu" <nusenu@openmailbox.org> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package?
(only found 28 relays)
+---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
For Debian-based systems, on the top of "/etc/apt/apt.conf.d/50unattended-upgrades" my file looks like this: Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}-security"; "${distro_id}:${distro_codename}-updates"; // "${distro_id}:${distro_codename}-proposed"; "${distro_id}:${distro_codename}-backports"; "TorProject:trusty"; }; The first 4 allowed origins are for official Ubuntu software for the version I'm running, and the last entry says to use the 'trusty' dist from the TorProject source. Here's the original thread where I learned the trick: https://ubuntuforums.org/showthread.php?t=1401845&p=10070689#post10070689 On 11/01/2016 12:44 AM, Greg wrote:
Hi, I'm very interested in setting up unattended upgrades for tor. I tried searching for instructions on how to do it. But the only instructions I could really find didn't work (on the Library Freedom git project). How do I write the config so that the tor repo (or whatever it's called) is updated by unattended upgrades? Thanks.
On Oct 26, 2016 1:23 AM, "nusenu" <nusenu@openmailbox.org <mailto:nusenu@openmailbox.org>> wrote:
> 32 relays updated (Debian + Tor compiled to latest version) > > I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package?
(only found 28 relays)
+---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thanks, Teor and SuperSluether. That's just what I needed, that TorProject:trusty syntax. Looks like it's working. -Greg On Tue, Nov 1, 2016 at 5:34 AM, SuperSluether <supersluether@gmail.com> wrote:
For Debian-based systems, on the top of "/etc/apt/apt.conf.d/50unattended-upgrades" my file looks like this:
Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}-security"; "${distro_id}:${distro_codename}-updates"; // "${distro_id}:${distro_codename}-proposed"; "${distro_id}:${distro_codename}-backports"; "TorProject:trusty"; };
The first 4 allowed origins are for official Ubuntu software for the version I'm running, and the last entry says to use the 'trusty' dist from the TorProject source.
Here's the original thread where I learned the trick: https://ubuntuforums.org/showthread.php?t=1401845&p=10070689#post10070689
On 11/01/2016 12:44 AM, Greg wrote:
Hi, I'm very interested in setting up unattended upgrades for tor. I tried searching for instructions on how to do it. But the only instructions I could really find didn't work (on the Library Freedom git project). How do I write the config so that the tor repo (or whatever it's called) is updated by unattended upgrades? Thanks.
On Oct 26, 2016 1:23 AM, "nusenu" <nusenu@openmailbox.org> wrote:
32 relays updated (Debian + Tor compiled to latest version)
I am getting too old for this without a server management system ....
not all relays with your contactinfo seem to be updated properly doing it manually is slow and error prone. Maybe consider using the 'unattended-upgrades' package?
(only found 28 relays)
+---------+---------------------+------------+ | version | nickname | restarted | +---------+---------------------+------------+ | 0.2.8.7 | niftychipmunk | 2016-10-26 | | 0.2.8.7 | niftymouse | 2016-10-26 | | 0.2.8.7 | niftygerbil | 2016-10-26 | | 0.2.8.7 | niftyquokka | 2016-10-26 | | 0.2.8.9 | testnode2 | 2016-10-23 | | 0.2.8.9 | DOESaDEworkWITHtor1 | 2016-10-20 | | 0.2.8.9 | niftypedetes | 2016-10-26 | | 0.2.8.9 | niftyeuropeanrabbit | 2016-10-26 | | 0.2.8.9 | niftychinchilla | 2016-10-26 | | 0.2.8.9 | 2ndTRYdeEXIT | 2016-10-20 | | 0.2.8.9 | niftysugarglider | 2016-10-26 | | 0.2.8.9 | niftyvolcanorabbit | 2016-10-26 | | 0.2.8.9 | niftyrat | 2016-10-26 | | 0.2.8.9 | niftypatagonianmara | 2016-10-25 | | 0.2.8.9 | niftywoodmouse | 2016-10-25 | | 0.2.8.9 | niftysquirrel | 2016-10-25 | | 0.2.8.9 | mullahspinymouse | 2016-10-26 | | 0.2.8.9 | niftybankvole | 2016-10-25 | | 0.2.8.9 | capespinymouse | 2016-10-26 | | 0.2.8.9 | niftyhedgehog | 2016-10-25 | | 0.2.8.9 | niftycapybara | 2016-10-26 | | 0.2.8.9 | testnode | 2016-10-23 | | 0.2.8.9 | cairospinymouse | 2016-10-26 | | 0.2.8.9 | niftykangaroorat | 2016-10-25 | | 0.2.8.9 | niftypika | 2016-10-26 | | 0.2.8.9 | niftyjerboa | 2016-10-26 | | 0.2.8.9 | niftyguineapig | 2016-10-26 | | 0.2.8.9 | niftycottontail | 2016-10-26 | +---------+---------------------+------------+
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (9)
-
Greg -
John Ricketts -
Juuso Lapinlampi -
Markus Koch -
nusenu -
Petrusko -
Roman Mamedov -
SuperSluether -
teor