Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-28 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by anarcat):

 just for the record, i didn't mean we should send lawyers to members of
 the community. i meant that if we get squatters that take over the domains
 for hostile purposes, we might have a legal recourse.

 apologies if i was misunderstood.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-28 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by ln5):

 * status:  new => closed
 * resolution:   => fixed


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-28 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+-
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ln5):

 Thanks for donating time and money to Tor Project. Unfortunately you're
 donating something that we no longer want.

 The decision made in our February meeting is documented here:
 
https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdminTeamMinutes#Domainportfoliolikeshouldwedrop.is
 The ticket dealing with this is #29390.

 Please stop serving torproject.fr and torproject.be. If possible, please
 keep the domains registered for "some time". Dropping the DNS requests on
 the floor is fine.

 Thanks again for your efforts and please accept my apologies for not
 reaching out to you earlier regarding  the .fr domain.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-27 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+-
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by goose):

 I have to say that i disagree with every single point you just made. If
 someone offers to pay for a torproject tld and even offers DNS control to
 the project then it should not be rejected. It is also not confusing at
 all if the domain name is integrated into the project's DNS. Everybody
 ends up at torproject.org, so what is the confusion all about ? In fact
 those domains make sure that people end up at the right place.

 Regarding the "not being renewd/squatting" point, i have to say that
 torproject.fr is working fine for a number of years right now and i just
 thought well i don't mind spending a few more bucks for .be. Somehow my
 domains are always paid for. It may be that other people don't take care
 of their domains however i am not one of "them". By far the worst argument
 was well we don't want those domains and if we don't like what we see we
 just send in the lawyers. That is just arrogant, ungreatful, expensive and
 unnecessary at least when it comes to the domains i'm responsible for.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-27 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+-
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 there's a potential infinity of such domain name. it's a difficult call to
 make, but once you start buying them, you might never stop because new
 TLDs will always come up. should we buy torproject.amazon? how about
 torproject.io? or torproject.in?

 my personal belief is that getting a larger variety of domain names only
 serves to confuse users about what the real hostname is. unless we have a
 purpose for the `.be`, we shouldn't be using it. if a new domain comes up
 that causes trouble, we can always take it down with trademark law,
 presumably.

 but i wasn't in fosdem so I haven't heard the other arguments. one problem
 with not renewing the existing domains is that they *will* be squatted
 (instead of just not answering) so there's that component as well.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns)

2019-05-17 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+-
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 And once a choice is made here, somebody should address #27720.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #27951 [Internal Services/Tor Sysadmin Team]: decide how to handle torproject.be (was: integrate torproject.be into our dns) (was: integrate torproject.be into our dns)

2019-05-17 Thread Tor Bug Tracker & Wiki
#27951: decide how to handle torproject.be (was: integrate torproject.be into 
our
dns)
-+-
 Reporter:  goose|  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arma):

 * owner:  (none) => tpa
 * component:  Internal Services => Internal Services/Tor Sysadmin Team


Comment:

 I'm retitling this one so it's clear that it's more about a decision than
 about an action.

 At the Fosdem meeting among the systems, the general consensus was that
 accumulating more and more torproject domains around the world wasn't
 really a sustainable plan, especially because there are confusing and
 indistinguishable ones like torproject.in that aren't being responsibly
 kept up to date.

 So I think the plan there might have been to discourage getting more
 torproject domains, and stop renewing existing ones (like torproject.is).

 All of that said, I am putting this in the tor sysadmin component so
 Anarcat and Linus and weasel can come to a consensus on what we decided.
 :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs