Re: [tor-relays] Proposing an Exit Node

2017-01-16 Thread grarpamp
I agree with you here. This is a mission, a partnership amongst all perticipants, even negotiated and discovered as such, to good ends and via good means, amongst similar, or amenable participants, with backbone, and with high principles. Yes toppost, shootme. On Tue, Jan 17, 2017 at 2:00 AM,

Re: [tor-relays] Proposing an Exit Node

2017-01-16 Thread grarpamp
On Tue, Jan 17, 2017 at 1:08 AM, Kenneth Freeman wrote: > On 01/16/2017 11:49 AM, Olaf Grimm wrote: >> Now I have my servers outside and at home a middle node only. > This is best practice. And even under a proposed corporate aegis (LLC, > you really need to be loaded for

Re: [tor-relays] Proposing an Exit Node

2017-01-16 Thread Roger Dingledine
On Mon, Jan 16, 2017 at 11:49:46PM -0700, Mirimir wrote: > Or you need adequate anonymity, and be willing to lose sunk cost. I think trying to run exit relays with anonymity, and with plans to discard them as needed, is a poor plan long-term. In the struggle for what the Internet can become, we

Re: [tor-relays] Proposing an Exit Node

2017-01-16 Thread Mirimir
On 01/16/2017 11:08 PM, Kenneth Freeman wrote: > > On 01/16/2017 11:49 AM, Olaf Grimm wrote: >> An exit node at home is funny. Last year I've got visitors from law >> enforcement early in the morning. Now I have some new "friends" from the >> police department. >> >> Be warned! They take a look

Re: [tor-relays] FW: What's a "useful" mailing list contributor? (was Re: What's a "useful" relay?)

2017-01-16 Thread Kenneth Freeman
Tor could use an Eternal September. On 01/16/2017 10:11 PM, grarpamp wrote: > I would support Rana's volunteer proposal as described, > and growing integration, as being a beneficial contribution. > Let us not forget, all begin as noobs to a norm, and full > normalization may be chilling to

[tor-relays] Proposing an Exit Node

2017-01-16 Thread Kenneth Freeman
On 01/16/2017 11:49 AM, Olaf Grimm wrote: > An exit node at home is funny. Last year I've got visitors from law > enforcement early in the morning. Now I have some new "friends" from the > police department. > > Be warned! They take a look on bad movies and assume you are the one... > > Now I

Re: [tor-relays] Uptime missing from Arm

2017-01-16 Thread Kenneth Freeman
On 01/16/2017 11:07 AM, Petrusko wrote: > To resume, > So it's working by cloning the git repository as you wrote. > chown -R debian-tor:debian-tor * > inside folders /stem and /nyx > > Then (relay with default control socket) > cd nyx > sudo -u debian-tor ./run_nyx This (or just "nyx")

Re: [tor-relays] FW: What's a "useful" mailing list contributor? (was Re: What's a "useful" relay?)

2017-01-16 Thread grarpamp
I would support Rana's volunteer proposal as described, and growing integration, as being a beneficial contribution. Let us not forget, all begin as noobs to a norm, and full normalization may be chilling to diversity. ___ tor-relays mailing list

Re: [tor-relays] exitnodes blocking services

2017-01-16 Thread George
Olaf Grimm: > An exit node at home is funny. Last year I've got visitors from law > enforcement early in the morning. Now I have some new "friends" from the > police department. > > Be warned! They take a look on bad movies and assume you are the one... > > Now I have my servers outside and at

Re: [tor-relays] assign_to_cpuworker failed

2017-01-16 Thread diffusae
Hi Felix, thanks for your answer. On 16.01.2017 18:49, Felix wrote: > There was similar on 027 but more massive including > * assign_to_cpuworker failed > * Your system clock just jumped > * stalling for seconds > Which is resolved since 0289. 'Address' was key. > > https://

Re: [tor-relays] exitnodes blocking services

2017-01-16 Thread Olaf Grimm
An exit node at home is funny. Last year I've got visitors from law enforcement early in the morning. Now I have some new "friends" from the police department. Be warned! They take a look on bad movies and assume you are the one... Now I have my servers outside and at home a middle node only.

[tor-relays] assign_to_cpuworker failed

2017-01-16 Thread Felix
Hi diffusae > The only warning I have found close to it: > > "Jan 13 11:08:46.000 [warn] Your system clock just jumped 216 seconds > forward; assuming established circuits no longer work" > > That could be due to the IPv4 autodetection? Maybe I should explicitly > set the Address option in