Re: [tor-relays] Moving my obfs4 bridge from tor expert bundle to Debian, and have some questions. Thanks.

[Keifer Bly]

Forgot to paste the unattended upgrades file sorry:

Unattended-Upgrade::Origins-Pattern {
"origin=Debian,codename=${distro_codename},label=Debian-Security";
"origin=TorProject";
};
Unattended-Upgrade::Package-Blacklist {
};
Unattended-Upgrade::Automatic-Reboot "true";





--Keifer



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Mar 29, 2020 at 10:45 PM Keifer Bly  wrote:

> Here is tors log:
>
> Mar 29 17:00:46.000 [notice] Tor 0.4.2.7 opening new log file.
> Mar 29 17:00:46.899 [notice] Tor 0.4.2.7 running on Linux with Libevent 
> 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
> Mar 29 17:00:46.900 [notice] Tor can't help you if you use it wrong! Learn 
> how to be safe at https://www.torproject.org/download/download#warning
> Mar 29 17:00:46.901 [notice] Read configuration file "/etc/tor/torrc".
> Mar 29 17:00:46.902 [notice] Your ContactInfo config option is not set. 
> Please consider setting it, so we can contact you if your server is 
> misconfigured or something else goes wrong.
> Mar 29 17:00:46.902 [notice] Based on detected system memory, MaxMemInQueues 
> is set to 6127 MB. You can override this by setting MaxMemInQueues by hand.
> Mar 29 17:00:46.905 [notice] Opening Control listener on 127.0.0.1:9050
> Mar 29 17:00:46.905 [notice] Opened Control listener on 127.0.0.1:9050
> Mar 29 17:00:46.906 [notice] Opening OR listener on 0.0.0.0:80
> Mar 29 17:00:46.907 [notice] Opened OR listener on 0.0.0.0:80
> Mar 29 17:00:46.908 [notice] Opening Extended OR listener on 127.0.0.1:0
> Mar 29 17:00:46.916 [notice] Extended OR listener listening on port 50727.
> Mar 29 17:00:46.917 [notice] Opened Extended OR listener on 127.0.0.1:50727
> Mar 29 17:00:46.000 [notice] Not disabling debugger attaching for 
> unprivileged users.
> Mar 29 17:00:46.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
> Mar 29 17:00:47.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
> Mar 29 17:00:47.000 [notice] Configured to measure statistics. Look for the 
> *-stats files that will first be written to the data directory in 24 hours 
> from now.
> Mar 29 17:00:47.000 [warn] You are running Tor as root. You don't need to, 
> and you probably shouldn't.
> Mar 29 17:00:47.000 [notice] You are running a new relay. Thanks for helping 
> the Tor network! If you wish to know what will happen in the upcoming weeks 
> regarding its usage, have a look at 
> https://blog.torproject.org/blog/lifecycle-of-a$Mar 29 17:00:47.000 [notice] 
> It looks like I need to generate and sign a new medium-term signing key, 
> because I don't have one. To do that, I need to load (or create) the 
> permanent master identity key. If the master identity key was not$Mar 29 
> 17:00:47.000 [notice] Your Tor server's identity key fingerprint is 'torland 
> 7DBC1875771B54F4FE40EB376460EF557EE9E884'
> Mar 29 17:00:47.000 [notice] Your Tor bridge's hashed identity key 
> fingerprint is 'torland 780F4E3ADBC574A63CE8155C0911E0A06BA3331D'
> Mar 29 17:00:47.000 [notice] Bootstrapped 0% (starting): Starting
> Mar 29 17:00:48.000 [notice] Starting with guard context "default"
> Mar 29 17:00:48.000 [notice] Registered server transport 'obfs4' at '[::]:443'
> Mar 29 17:00:50.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
> Mar 29 17:00:51.000 [notice] Bootstrapped 10% (conn_done): Connected to a 
> relay 
>   
>Mar 29 17:00:51.000 [notice] Bootstrapped 14% (handshake): Handshaking 
> with a relay  
>   
>   Mar 29 17:00:51.000 [notice] Bootstrapped 15% (handshake_done): 
> Handshake with a relay done
> Mar 29 17:00:51.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough 
> directory info to build circuits
> Mar 29 17:00:51.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake 
> finished with a relay to build circuits
> Mar 29 17:00:51.000 [notice] Bootstrapped 95% (circuit_create): Establishing 
> a Tor circuit
> Mar 29 17:00:52.000 [notice] Guessed our IP address as 24.176.251.66 (source: 
> 107.189.10.156).
> Mar 29 17:00:53.000 [notice] Bootstrapped 100% (done): Done
> Mar 29 17:00:53.000 [notice] Now checking whether ORPort 24.176.251.66:80 is 
> reachable... (this may take up to 20 minutes -- look for log messages 
> indicating success)
> Mar 29 17:00:54.000 [notice] Self-testing indicates your ORPort is reachable 
> from the outside. Excellent. Publishing server descriptor.
> Mar 29 17:01:00.000 [notice] Performing bandwidth 

Re: [tor-relays] Moving my obfs4 bridge from tor expert bundle to Debian, and have some questions. Thanks.

[teor]

Hi,

> On 30 Mar 2020, at 13:45, Keifer Bly  wrote:
> So I am switching the OBFS4 bridge I was running via Tor Expert Bundle on 
> Windows 10 over to running it via Debian app for Windows 10.
> 
> This app is on the Windows store at 
> https://www.microsoft.com/en-us/p/debian/9msvkqc78pk6?activetab=pivot:overviewtab
> 
> Essentially, it is an app that lets you run Linux packages on Windows. I made 
> the switch so that I could keep tor and obfs4 up to date using unattended 
> upgrades.
> 
> However, for some odd reason, despite the fact I backed up the tor identity 
> keys and pasted them into the keys directory when I moved over, the bridge is 
> still generating new keys on startup. I copied the key files from my expert 
> bundle bridge to
> 
> /var/lib/tor/keys directory in the Linu terminal, I copied all of the files. 
> It’s a bridge so no big deal I guess, but wonder why that is happening.
> 
Please show us the tor logs.
> https://metrics.torproject.org/rs.html#details/780F4E3ADBC574A63CE8155C0911E0A06BA3331D
> 
> And, I tested to see of unattended upgrades was working correctly after 
> configuring it with these instructions:
> 
> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates
> 
>  
> 
> And got this the attached photo as a result, does this mean it is keeping tor 
> and obfs4 up to date?
> 
>  tor update test.PNG
> 

Please use a pastebin for logs, or paste the text in your email.
https://paste.debian.net is good.

Looks like updates aren't working, do you see the line that says:
Sanity check failed

T___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Moving my obfs4 bridge from tor expert bundle to Debian, and have some questions. Thanks.

[Keifer Bly]

Hi all,



So I am switching the OBFS4 bridge I was running via Tor Expert Bundle on
Windows 10 over to running it via Debian app for Windows 10.



This app is on the Windows store at
https://www.microsoft.com/en-us/p/debian/9msvkqc78pk6?activetab=pivot:overviewtab



Essentially, it is an app that lets you run Linux packages on Windows. I
made the switch so that I could keep tor and obfs4 up to date using
unattended upgrades.



However, for some odd reason, despite the fact I backed up the tor identity
keys and pasted them into the keys directory when I moved over, the bridge
is still generating new keys on startup. I copied the key files from my
expert bundle bridge to

/var/lib/tor/keys directory in the Linu terminal, I copied all of the
files. It’s a bridge so no big deal I guess, but wonder why that is
happening.

https://metrics.torproject.org/rs.html#details/780F4E3ADBC574A63CE8155C0911E0A06BA3331D



And, I tested to see of unattended upgrades was working correctly after
configuring it with these instructions:





https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpdates



And got this the attached photo as a result, does this mean it is keeping
tor and obfs4 up to date?



Thanks very much.



 tor update test.PNG


--Keifer
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] BadExit

[teor]

Hi Georg,

> On 27 Mar 2020, at 22:40, Georg Koppen  wrote:
> 
>> (If the DNS for the site they are testing has both IPv4 and IPv6, then
>> the outcome will depend on their tor version and config. 0.4.3 and
>> later will prefer IPv6 by default.)
> 
> Not sure what Arthur is running but I am just using what Debian ships on
> the box I run the tests, which is currently 0.3.5.8. I guess it might be
> worth thinking about switching away from that. Maybe tracking and using
> the version Tor Browser ships is smarter?

I think any supported Tor version is ok.

But yes, using the same version as Tor Browser users could be helpful.

T
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Possible to run a tor bridge/relay via tor browser?

[teor]

Hi,

> On 28 Mar 2020, at 05:14, Keifer Bly  wrote:
> 
> ServerTransportPlugin obfs4 exec C:\Users\keife\Desktop\Tor Browser test 
> relay\Browser\TorBrowser\Tor\PluggableTransports

You might need to quote the spaces in this path. And specify the path to
the binary, not the directory.

Try running tor in a terminal, so you can see the logs.

T
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Problem with ubuntu 18.04 x386

[Nuno Rego]

I had a similar problem on a server and solved it by disabling IPV6.

Cumprimentos;
Nuno

-- 
Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
https://tutanota.com



Mar 29, 2020, 07:31 by francisc...@protonmail.com:

> I make the installation following the official page torproject.org from the 
> tor repositories. 
>
> I edit de torrc file and save the changes. but when i restart the service, 
> gives me error. 
>
> $ systemctl status tor@default
> failed (Result: exit-code) since... 
>
> systemd[1]: tor@default.service: Start request repeated too quickly. 
> systemd[1]: tor@default.service: Failed with result 'exit-code'. 
> systemd[1]: Failed to start Anonymizing overlay network for TCP. 
>
> thanks in advance. 
>
>
> Sent from ProtonMail mobile
>
>

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Problem with ubuntu 18.04 x386

[Francisco]

orrc file and save the changes. but when i restart the service, 
> gives me error.
>
> $ systemctl status tor@default
> failed (Result: exit-code) since...
>
> systemd[1]: tor@default.service: Start request repeated too quickly.
> systemd[1]: tor@default.service: Failed with result 'exit-code'.
> systemd[1]: Failed to start Anonymizing overlay network for TCP.
>
> thanks in advance.
>
> Sent from ProtonMail mobile
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> http://lists.torproject.org/pipermail/tor-relays/attachments/20200329/567bd928/attachment-0001.html
>
> --
>
> Message: 2
> Date: Sun, 29 Mar 2020 10:50:43 +0200
> From: TorGate torg...@linux-hus.dk
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays] Problem with ubuntu 18.04 x386
> Message-ID: 7a4a45f0-43b2-415b-9e01-77b55bb04...@linux-hus.dk
> Content-Type: text/plain; charset="utf-8"
>
> what says the logfile ?
> tor version ?
>
> > Am 29.03.2020 um 08:31 schrieb Francisco francisc...@protonmail.com:
> > I make the installation following the official page torproject.org from the 
> > tor repositories.
> > I edit de torrc file and save the changes. but when i restart the service, 
> > gives me error.
> > $ systemctl status tor@default
> > failed (Result: exit-code) since...
> > systemd[1]: tor@default.service: Start request repeated too quickly.
> > systemd[1]: tor@default.service: Failed with result 'exit-code'.
> > systemd[1]: Failed to start Anonymizing overlay network for TCP.
> > thanks in advance.
> > Sent from ProtonMail mobile
> >
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
> -- next part --
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: Message signed with OpenPGP
> URL: 
> http://lists.torproject.org/pipermail/tor-relays/attachments/20200329/295a683f/attachment-0001.sig
>
> --
>
> Subject: Digest Footer
>
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> --
>
> End of tor-relays Digest, Vol 110, Issue 33


___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Problem with ubuntu 18.04 x386

[teor]

Hi,

> On 30 Mar 2020, at 12:46, Nuno Rego  wrote:
> 
> I had a similar problem on a server and solved it by disabling IPV6.

Yes, a lot of people struggle to configure IPv6. Or their providers
don't route IPv6 correctly.

We're working on some changes to tor, to help diagnose IPv6
connection issues.

T
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Problem with ubuntu 18.04 x386

[teor]

Hi,

> On 30 Mar 2020, at 12:45, Francisco  wrote:
> 
> Hi, sorry for that, I'm sending more information now:
> 
> Tor version:
> Tor 0.4.2.7 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1, Zlib 
> 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3.
> 
> The log when I try to restart the service (sudo systemctl restart 
> tor@default) :
> Job for tor@default.service failed because the control process exited with 
> error code.
> See "systemctl status tor@default.service" and "journalctl -xe" for details.

Thanks for these extra systemd logs.

But we need to see the detailed tor logs.
Try /var/log/tor/log, or similar?

T


___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Problem with ubuntu 18.04 x386

[Kat Kat]

Hi, I've encountered this. There is a wait period before you can start tor.
Try systemctl restart tor

On Sun, Mar 29, 2020, 3:50 AM TorGate  wrote:

> what says the logfile ?
> tor version ?
>
> > Am 29.03.2020 um 08:31 schrieb Francisco :
> >
> > I make the installation following the official page torproject.org from
> the tor repositories.
> >
> > I edit de torrc file and save the changes. but when i restart the
> service, gives me error.
> >
> > $ systemctl status tor@default
> > failed (Result: exit-code) since...
> >
> > systemd[1]: tor@default.service: Start request repeated too quickly.
> > systemd[1]: tor@default.service: Failed with result 'exit-code'.
> > systemd[1]: Failed to start Anonymizing overlay network for TCP.
> >
> > thanks in advance.
> >
> >
> > Sent from ProtonMail mobile
> >
> >
> > ___
> > 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

Re: [tor-relays] Problem with ubuntu 18.04 x386

[TorGate]

what says the logfile ?
tor version ?

> Am 29.03.2020 um 08:31 schrieb Francisco :
> 
> I make the installation following the official page torproject.org from the 
> tor repositories.
> 
> I edit de torrc file and save the changes. but when i restart the service, 
> gives me error.
> 
> $ systemctl status tor@default
> failed (Result: exit-code) since...
> 
> systemd[1]: tor@default.service: Start request repeated too quickly.
> systemd[1]: tor@default.service: Failed with result 'exit-code'.
> systemd[1]: Failed to start Anonymizing overlay network for TCP.
> 
> thanks in advance.
> 
> 
> Sent from ProtonMail mobile
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays



signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Problem with ubuntu 18.04 x386

[Francisco]

I make the installation following the official page torproject.org from the tor 
repositories.

I edit de torrc file and save the changes. but when i restart the service, 
gives me error.

$ systemctl status tor@default
failed (Result: exit-code) since...

systemd[1]: tor@default.service: Start request repeated too quickly.
systemd[1]: tor@default.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Anonymizing overlay network for TCP.

thanks in advance.

Sent from ProtonMail mobile___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays