[tor-relays] Auto Upgrading Tor Using Unattended Ugrades
Keifer Bly
keifer.bly at gmail.com
Mon May 27 20:18:10 UTC 2019
Hello all,
So I am now auto upgrading tor using the method at
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates
Upon testing, this is what I got.
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: []
Checking: firefox-esr ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: google-cloud-sdk ([<Origin component:'main'
archive:'cloud-sdk-stretch' origin:'cloud-sdk-stretch'
label:'cloud-sdk-stretch' site:'packages.cloud.google.com' isTrusted:True>])
Checking: google-compute-engine ([<Origin component:'main'
archive:'google-compute-engine-stretch-stable'
origin:'google-compute-engine-stretch-stable'
label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com'
isTrusted:True>])
Checking: google-compute-engine-oslogin ([<Origin component:'main'
archive:'google-compute-engine-stretch-stable'
origin:'google-compute-engine-stretch-stable'
label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com'
isTrusted:True>])
Checking: libavcodec57 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libavfilter6 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libavformat57 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libavresample3 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libavutil55 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libpostproc54 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libswresample2 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: libswscale4 ([<Origin component:'main' archive:'stable'
origin:'Debian' label:'Debian-Security' site:'security.debian.org'
isTrusted:True>])
Checking: python-google-compute-engine ([<Origin component:'main'
archive:'google-compute-engine-stretch-stable'
origin:'google-compute-engine-stretch-stable'
label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com'
isTrusted:True>])
Checking: python3-google-compute-engine ([<Origin component:'main'
archive:'google-compute-engine-stretch-stable'
origin:'google-compute-engine-stretch-stable'
label:'google-compute-engine-stretch-stable' site:'packages.cloud.google.com'
isTrusted:True>])
pkgs that look like they should be upgraded:
Fetched 0 B in 0s (0 B/s)
fetch.run() result: 0
blacklist: []
whitelist: []
No packages found that can be upgraded unattended and no pending
auto-removals
What I am attempting to do is automatically install new tor versions when
they are released. Will this do that automatically? How can I keep this
process running? Thanks.
--Keifer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20190527/7bdcc3c7/attachment.html>
More information about the tor-relays
mailing list