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 <[email protected]> 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" <[email protected]> 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 > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > > _______________________________________________ > tor-relays mailing > [email protected]https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > _______________________________________________ > tor-relays mailing list > [email protected] > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >
_______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
