Re: [tor-relays] Protecting the bridge port from active probes

Dmitrii Tcvetkov wrote: > On Thu, 28 Mar 2019 17:08:38 + > Marek Szuba wrote: > > > Anyway, here is my logic. In order to operate properly, my bridge must > > have its ORPort reachable from the Internet. > > I might be wrong, but I got impression that if bridge is using > pluggable transpor

Re: [tor-relays] Relay without OpenSSL

> I'd like to add that it's only a warning and my new relay seems to work > so far: > > https://metrics.torproject.org/rs.html#details/839B17C459BCE9FD5178ABD4B2E3493379EC3419 > I spoke too soon. It went down shortly after my previous email and it never went back up. PS See some of you in an

Re: [tor-relays] Relay without OpenSSL

Matthew Finkel wrote: > I opened #29241 for this (because I didn't see anyone else open it). Thank you! I couldn't submit because trac doesn't accept my password anymore. I'd like to add that it's only a warning and my new relay seems to work so far: https://metrics.torproject.org/rs.html#detail

[tor-relays] Relay without OpenSSL

I recently tried updating one of my relays to Tor 0.4.0.1 compiled with NSS (and without OpenSSL) but it failed to start, see the logs below. I wonder if this configuration is supported at all and whether I should try running a brand new relay instead of updating? Alex [warn] connection_or_comput

Re: [tor-relays] "Your IP seems to have changed" notice

teor wrote: > Your relay uses its local resolver to discover its own IP address. > It doesn't ask an exit. My local resolver was dnsmasq and it was configured to forward all requests to port 9053. I updated /etc/hosts and added a special rule for my domain in dnsmasq.conf. This should fix the iss

Re: [tor-relays] "Your IP seems to have changed" notice

Alexander Nasonov wrote: > This morning (9:30 UTC), my relay (nebo.xmmswap.com) printed > > 09:30:08.000 Your IP seems to have changed to <> > (METHOD=GETHOSTNAME HOSTNAME=nebo). Updating. It looks like a bad exit because my local resolver is configured to use a different t

[tor-relays] "Your IP seems to have changed" notice

This morning (9:30 UTC), my relay (nebo.xmmswap.com) printed 09:30:08.000 Your IP seems to have changed to <> (METHOD=GETHOSTNAME HOSTNAME=nebo). Updating. 09:30:08.000 Our IP Address has changed from 217.182.198.76 to <>; rebuilding descriptor (source: METHOD=GETHOSTNAME HOSTNAME=nebo). ... Si

[tor-relays] my relay 'alnsn' died

B9A41AD7AE8B2A4E6DE96EE77E3C8C04BADA8AC0 is currently down because harware died this morning. I will either reinstall it or move to a different AS. In any case, it won't happen tomorrow. I hope to have it up and running on the weekend. Master key is safe because it's on a different machine. Alex

Re: [tor-relays] Tor exit nodes attacking SSH?

m...@eugenemolotov.ru wrote: > Make a "trap" ssh server (for example on virtualbox machine > without any sensitive data) and log in into it through tsocks. > After that check from which ip it was logged in. This probably > would be ip of the exit node. What if they "bridge" mitm-ed traffic to a di

Re: [tor-relays] Go home GeoIP, you're drunk.

Andreas Krey wrote: > NSA: There are people excluding US exits? Just let's set some > of ours to india. (Where that is probably not their modus Tor enthusiasts: Hmm, advertised country doesn't match GeoIP, let's take a closer look ... > When twitter notices one of their users always comes via tor

Re: [tor-relays] Go home GeoIP, you're drunk.

teor wrote: > For example, I run an exit in Canada, where some addresses were allocated > from an Canadian block, and others were allocated from a US block. So if > I wanted to, I could ORPort on a Canadian address, and Exit on a US one. It sounds like a country should be set by an operator in tor

Re: [tor-relays] Go home GeoIP, you're drunk.

Ralph Seichter wrote: > I moved a Tor relay to new hardware, keeping the keys. Both old and new > server are located in Germany and provided by the same hosting company. > After the latest Atlas update, I was surprised to see that the IPv4 > address is listed as belonging to an AS in Ukraine. A lit

Re: [tor-relays] Tor relay dying in FreeBSD

Farid Joubbi wrote: > Jul 12 23:44:24.672 [warn] You appear to lack permissions to change memory > limits. Are you root? > Jul 12 23:44:24.672 [warn] Unable to raise RLIMIT_MEMLOCK: Operation not > permitted Read about login classes. Starting points: man login.conf man cap_mkdb man chfn -- Al

Re: [tor-relays] keypair does not match its older value

nusenu wrote: > Alexander Nasonov: > > Hi, > > > > I tried moving a tor relay with offline master key to a new host but > > something went wrong and it printed several warnings: > > > > http status 400 ("Looks like your keypair does not match its

Re: [tor-relays] keypair does not match its older value

Hi Roger, Roger Dingledine wrote: > On Tue, Jun 20, 2017 at 11:04:31PM +0100, Alexander Nasonov wrote: > > I tried moving a tor relay with offline master key to a new host but > > something went wrong and it printed several warnings: > > > > http status 400 ("

[tor-relays] keypair does not match its older value

Hi, I tried moving a tor relay with offline master key to a new host but something went wrong and it printed several warnings: http status 400 ("Looks like your keypair does not match its older value.") response from dirserver What did I screw up and how to fix this problem if it happends again