Re: [tor-relays] Upgrading a relay and changing IP address

[teor]

> On 24 May 2017, at 17:27, Jan Welker  wrote:
> 
>> Again, sorry about the lack of notification. It's a big job, and
>> I was short on time this time around.
>> 
>> I would love someone to volunteer to notify all the fallback directory
>> operators: the list only changes once every 6-12 months.
> 
> What would that involve if someone decides to volunteer?
> 
>- Generating a list with the email address per relay

You can get the fingerprints from:
https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc
And then write a quick script to get the contact details.

Or use the instructions at:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors#d.InformingRelayOperators
To modify the script at:
https://gitweb.torproject.org/tor.git/tree/scripts/maint/updateFallbackDirs.py

(No one has automated that yet, but we are close: we just need to
do something like the check_existing mode that outputs contacts.)

>- Sending an email to the Operator

Most operators change their email address to avoid spam.
You will need to work out what each address is.

It is ok to send one email, and BCC all the operators.
Put me in To: or CC: please.
And then send a copy to tor-relays saying that's what you
sent to all the operators.

https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors#GroupEmails

>- Updating the list with the operators and their answer

If you open a ticket with a list of opt-outs, I will fix this up
when we next rebuild the list.

>- (Dealing with all the unreachable addresses)

That's ok, as long as the relay has the same details, I don't worry
about emails that bounce.

> And the list contains between 150 and 200 fallback dirs.

Yes.

When we go looking for new fallback operators, we do a similar thing
for all relays that are *not* on the list, and have good bandwidth and
uptime.

T
--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org




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

Re: [tor-relays] Memory Problems with tor releay

[Roger Dingledine]

On Wed, May 24, 2017 at 08:49:38PM +0200, tor-relay.d...@o.banes.ch wrote:
> Hello Roger,
> 
> I updated the ticket. You will find the output of the valgrind there as
> well:
> https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.txt

Well, you are a winner, in that you found a new Tor bug (in
0.3.1.1-alpha):
https://bugs.torproject.org/22368

Once we resolve that one, I'll ask for another valgrind run. :)

--Roger

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

Re: [tor-relays] Memory Problems with tor releay

[tor-relay . dirk]

Hello Roger,

I updated the ticket. You will find the output of the valgrind there as
well:
https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.txt

best regards

Dirk

On 23.05.2017 06:00, Roger Dingledine wrote:
> On Tue, May 23, 2017 at 03:01:10AM +, John Ricketts wrote:
>> Roger,
>>
>> I have whatever resources you need for testing.  Let me know if you would 
>> like them.
> 1)
> git clone https://git.torproject.org/git/tor
> cd tor.git
> ./autogen.sh && ./configure && make
>
> 2) edit /etc/security/limits.conf to have "tord hard nofile 65536" and
> "tord soft nofile 65536" lines, where tord is your user who will run it.
>
> 3)
> valgrind --leak-check=yes --error-limit=no --undef-value-errors=no src/or/tor 
> orport 9001 dirport 9030 nickname sorryitsslow geoipfile src/config/geoip
>
> (You might also want to set datadirectory, etc if you prefer, or point
> it to a torrc file if you prefer. Once you've got it working, you might
> run it with a datadirectory that has keys for an established relay.)
>
> Then watch the output for interesting valgrind complaints (I don't
> expect any, but if you find some, great!), and when you've let it
> run for a while, ^C it, let it close down, and see if Valgrind tells
> you about any "definite" memory leaks.
>
> Be aware that unless the CPU is super amazing, it will be totally cpu
> saturated and constantly failing to keep up with the requests it receives.
> So it is a fine thing to do for active bug hunting, but somewhat rude to
> do on real relays. :)
>
> --Roger
>
> ___
> 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] Upgrading a relay and changing IP address

[Cristian Consonni]

On 24/05/2017 03:25, teor wrote:
>> On 24 May 2017, at 01:05, Cristian Consonni  wrote:
>> I am a little bit perplexed because I responded to a call for fallback
>> dirs last December (Dec 2016), but then I got no answer or confirmation
>> that the relay was elected to become a fallback dir and so I assumed it
>> was not.
> 
> Sorry about that, I tried to BCC all the fallback operators the first
> few times we changed the list.
> 
> But it is a lot of work, and sometimes spam filters eat the email
> anyway.
> 
> So this time I just announced it on tor-relays:
> https://lists.torproject.org/pipermail/tor-relays/2017-May/012285.html

No worries :-)

>> Now, from this list[1] I see that it has the FallbackDir flag.
>>
>> So, again, in this case I should try to keep the same IP address when
>> upgrading, right?
> 
> Please keep the same IP address, ports, and RSA and ed25519 keys
> (fingerprint).

I'll do.

Cristian




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

Re: [tor-relays] Doing the english [Was: Kitten1 and kitten2 compromised (guard/hs/fallback directory)]

[r1610091651]

Also explained by British dictionary:
https://www.merriam-webster.com/words-at-play/flammable-or-inflammable

Cheers

On Wed, 24 May 2017 at 02:03 Torix  wrote:

> I was told in 1955 that "flammable" was invented to put on trucks because
> so many people - including many truck drivers - thought that inflammable
> meant "not flammable".  Like independent vs. dependent, indivisble vs.
> divisible etc.
>
>
> Sent with ProtonMail  Secure Email.
>
>  Original Message 
> Subject: Re: [tor-relays] Doing the english [Was: Kitten1 and kitten2
> compromised (guard/hs/fallback directory)]
> Local Time: May 21, 2017 11:22 AM
> UTC Time: May 21, 2017 3:22 PM
> From: pipat...@gmail.com
> To: tor-relays@lists.torproject.org
>
> On Sun, May 21, 2017 at 5:16 PM, Ian Zimmerman  wrote:
> > On 2017-05-20 18:07, Chris Kerr wrote:
> >
> >> Yes, 'sensible', like 'actually' and 'eventually', is a "false friend"
> >> whose meaning in English is different from that in just about every
> >> other European language (but the other languages are consistent with
> >> each other e.g. 'sensible' in French and 'sensibel' in German have
> >> the same meaning), which sometimes leads to confusion. Even more
> >> confusingly, 'insensible' is not the opposite of 'sensible' but rather
> >> means either 'imperceptible' or 'unconscious'.
> >
> > I have mused about this myself. The most curious thing is that English
> > is not even consistent with itself here. Think about the title of a
> > famous enlightenment era novel. The meaning of the nouns is precisely
> > inverted from the adjectives.
>
> Inflammable means flammable? What a country!
> ___
> 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] Upgrading a relay and changing IP address

[Jan Welker]

Hi Theor,

> Again, sorry about the lack of notification. It's a big job, and
> I was short on time this time around.
> 
> I would love someone to volunteer to notify all the fallback directory
> operators: the list only changes once every 6-12 months.

What would that involve if someone decides to volunteer?

- Generating a list with the email address per relay
- Sending an email to the Operator
- Updating the list with the operators and their answer
- (Dealing with all the unreachable addresses)

And the list contains between 150 and 200 fallback dirs.

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