Re: [tor-dev] Tor Relay Guide Disagreements

2018-08-03 Thread nusenu
> Going forward I'd propose the following to minimize the fraction and overhead:
> 
> I assume you maintain:
> /TorRelayGuide-ptbr
> /TorRelayGuide/OpenBSD
> /TorRelayGuide/NetBSD
> /TorRelayGuide/DragonFlyBSD
> 
> 
> I'll keep maintaining:
> /TorRelayGuide
> /TorRelayGuide/DebianUbuntu
> /TorRelayGuide/CentOSRHEL
> /TorRelayGuide/Fedora
> /TorRelayGuide/FreeBSD
> /TorRelayGuide/openSUSE
  /BSDUpdates (I might split that so we can assign that as easily as the rest)

-- 
https://twitter.com/nusenu_
https://mastodon.social/@nusenu



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


Re: [tor-dev] Tor Relay Guide Disagreements

2018-08-03 Thread grarpamp
> /TorRelayGuide
> /TorRelayGuide/DebianUbuntu

The former, in context wiith the latter, cannot be
treated as both a file and a directory (hier) by web
mirror / archvers such as wget onto disk.
And wiki / trac exports aren't available either :(
So instead push the page down into the hier,
thus ensuring safely collision free, like...

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


[tor-dev] Tor Relay Guide Disagreements

2018-08-03 Thread nusenu
Hi Vinícius,

(moving this discussion to the tor-dev mailing list since this isn't limited to 
the OpenBSD ticket scope
https://trac.torproject.org/projects/tor/ticket/26619#comment:14 )

Vinícius wrote:
>  you [nusenu] took over /FreeBSD, /BSDUpdates, and /OpenBSD and enabled the 
> 'read-
>  only' mode all by yourself without even consulting the original author or
>  anyone else 
[...]
>  is there any particular reason why you enabled the read-only mode on
>  /FreeBSD, /BSDUpdates, and /OpenBSD? I think this a pretty odd behavior.
>  I'm sorry. if you do want to own all these pages (and many other more),
>  please tell us. 

The Tor Relay Guide wiki page [1] has been 'read-only' pretty much since we 
launched it, it has been decided
a few months ago in [0]. Anyway read-only mode shouldn't affect you personally. 
Since you are listed on the tor people page 
I assume you can simply ask for the permissions to edit 'read-only' pages.

I'd still ask you to open tickets for changes like your change to the FreeBSD 
page instead of applying them directly so we can discuss them
before applying and to avoid the necessary efforts.


On 2018-07-10 I split out the OS specific instructions into their subpages:
/DebianUbuntu
/FreeBSD
...

because of this move content that was previously read-only until then became 
writable
but that wasn't an intentional step.

On 2018-08-02 you changed the FreeBSD page [4], here are two lines (examples) 
of your replacements:

my text:
change the nickname "myNiceRelay" to a name that you like
Change the email address bellow and be aware that it will be published

got replaced with:
CHANGE THE NICKNAME
WRITE YOUR EMAIL ADDRESS

I'm not sure I would consider these replacements an improvement since they 
remove
information without giving any reasoning for removing it in the comment.
Besides the removal of information this also introduces inconsistency in the 
torrc file we used so far in the guide.

I reverted your change and addressed the issue you brought up 
(net.inet.ip.random_id ordering, /etc/pkg/FreeBSD.conf modification)
and made the content read-only again (like it was until 2018-07-10).


>  ggus is that page's [/OpenBSD]  author and he allowed me to edit the 
> contents of that
>  page (the same is also applied to the /FreeBSD page; 

There has been no comment by ggus on #26619 (/OpenBSD) for a month so I went 
ahead and assigned it to me,
but I'll pull out of that ticket now.
https://trac.torproject.org/projects/tor/ticket/26619
ggus didn't create /FreeBSD [3].


> should we always open tickets with suggestions? - sadly it
>  also sounds extra odd, because when I did open tickets (#27006 and
>  #27007), a few minutes later you changed contents all by yourself 

#27006 is about /DragonFlyBSD
I've never touched that page?
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DragonFlyBSD?action=history

#27007 was about creating /NetBSD - which you did.

I didn't consider my change - where I replaced the ORPort to use 443 (because
we used that port everytime that works out of the box on a platform) 
to be part of the "create the /NetBSD page":
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/NetBSD?action=diff=2


Going forward I'd propose the following to minimize the fraction and overhead:

I assume you maintain:
/TorRelayGuide-ptbr
/TorRelayGuide/OpenBSD
/TorRelayGuide/NetBSD
/TorRelayGuide/DragonFlyBSD


I'll keep maintaining:
/TorRelayGuide
/TorRelayGuide/DebianUbuntu
/TorRelayGuide/CentOSRHEL
/TorRelayGuide/Fedora
/TorRelayGuide/FreeBSD
/TorRelayGuide/openSUSE

All pages should be read-only and writable to authorized users/maintainer, 
but feel free to have the pages you maintain world writable.

All non-maintainer changes are expected to go through a ticket.
After a timeout of 7 days with no maintainer response the ticket opener might
proceed with applying the proposed change.
I'll propose a list of requirements for a platform to be listed on the main 
page.

kind regards,
nusenu

[0] https://trac.torproject.org/projects/tor/ticket/24497
[1] https://trac.torproject.org/projects/tor/wiki/TorRelayGuide
[2] https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD
[3] 
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD?action=history
[4] 
https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD?sfp_email=_mail==diff=2_version=1


-- 
https://twitter.com/nusenu_
https://mastodon.social/@nusenu



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


Re: [tor-dev] WTF-PAD and the future

2018-08-03 Thread Mike Perry
Hi Yawning!

Yawning Angel:
> On 08/02/2018 08:26 PM, Mike Perry wrote:
> > Should we consider recommending basket2 also?
> 
> No.
> 
> > Is anyone running bridges with it? Probably not, I guess :/.
> 
> No one should be, it is incomplete, buggy, and needs a re-design.

Thanks for the heads up.
 
> As a side note, I question the utility of a PT that has the AGPL3
> network interaction requirement, though there is an exception for
> bridges distributed via BridgeDB and those shipped with Tor Browser.

Would you recommend anything else other than obfs4 at this time, as per
that README_SECURITY doc?
(https://github.com/mikeperry-tor/vanguards/blob/master/README_SECURITY.md)


-- 
Mike Perry


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


Re: [tor-dev] WTF-PAD and the future

2018-08-03 Thread Yawning Angel
On 08/02/2018 08:26 PM, Mike Perry wrote:
> Should we consider recommending basket2 also?

No.

> Is anyone running bridges with it? Probably not, I guess :/.

No one should be, it is incomplete, buggy, and needs a re-design.

As a side note, I question the utility of a PT that has the AGPL3
network interaction requirement, though there is an exception for
bridges distributed via BridgeDB and those shipped with Tor Browser.

Regards,

-- 
Yawning Angel



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