<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title></title>
</head>
<body>
<div> 
<div>
<div>Am Montag, 12. Februar 2018 um 12:33 schrieb nusenu <nusenu-lists@riseup.net>:
<br />
 </div>
<blockquote type="cite">
<div>
<blockquote type="cite">
<blockquote type="cite">If you block the ORPort, won't the reachability check fail?</blockquote>

<br />
Fine question. At least this has been the case in the past, though I
<br />
know there was discussion and maybe development to overcome this
<br />
weakness. But even if it's not possible yet, having bridge contact
<br />
information would allow us in the _future_ to reach out to bridge
<br />
operators to inform them that they don't have to keep their OR port open
<br />
anymore, and maybe even shouldn't.
<br />
 </blockquote>

<br />
https://trac.torproject.org/projects/tor/ticket/7349
<br />
https://trac.torproject.org/projects/tor/ticket/17159</div>
</blockquote>

<br />
Sorry, I'm not sure where to ask this questions
<br />
but reading this thread I realizes that I misunderstood this howto:
<br />
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy
<br />
<br />
Is it necessary for the ExtOrPort to be random?
<br />
Does the port change automatically?
<br />
Is it possible to specify the port?
<br />
<br />
And how can the wiki pages be changed?
<br />
<br />
Thanks :)
<br />
<br />
<br />
<br />
<br />
<br />
<br />
 
<blockquote type="cite">
<div><br />
--
<br />
https://mastodon.social/@nusenu
<br />
twitter: @nusenu_
<br />
<br />
_______________________________________________
<br />
tor-relays mailing list
<br />
tor-relays@lists.torproject.org
<br />
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</div>
</blockquote>
</div>
</div>
</body>
</html>