[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Tor relay says it is reachable, but is not appearing on the network.



Hi, 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


On Fri, May 24, 2019 at 12:38 AM Conrad Rockenhaus <conrad@xxxxxxxxxxxxxx> wrote:
Hello,

My bust, confirmation bias.

Thanks,

Conrad

On Thu, May 23, 2019 at 11:45 PM teor <teor@xxxxxxxxxx> wrote:
Hi,

> On 24 May 2019, at 14:08, Conrad Rockenhaus <conrad@xxxxxxxxxxxxxx> wrote:
>
> In April 2018 Google released an update that caused VPNs and Tor services to stop working on GCE and App Engine. It was a long planned network update.
>
> The following ticket refers: https://trac.torproject.org/projects/tor/ticket/25804

That ticket is about domain-fronting, which is used by meek and snowflake bridges.
But these issues do not affect other relays.

Do you have any information about Google blocking relays?

T
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
--
Conrad Rockenhaus
https://www.rockenhaus.com
Cell: (254) 292-3350
Fax: (254) 875-0459
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays