-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Well, people suggest that, unless you give <100KB/s, you should run a
relay, not a bridge, as more relays are used (and we have Tor weather
and such). You should be using Tor's daemon (apt-get install tor
tor-arm) for the relay or bridge itself.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Thanks for this. But why do you want to run your bridge instance among
the same Tor daemon as the one handling Tor Browser?
If you are on Debian, install Tor package separately with apt-get
install tor (recommended you add deb.torproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
BTW to all people,
I asked yesterday about Tor Weather, and why it wouldn't locate my
relay. It now can
(https://atlas.torproject.org/#details/9CBD228738FBB0293A348680DF241B606
069E2F9),
I just had to wait a day.
Hope this helps anyone who had these
This may be a naïve question, but I've fired up my 64-bit Debian box now
that the nights are cool, and editing the torrc to establish a bridge
relay borks the browser. I provide anonymity much more than I use it
myself, but is the bridge relay copacetic? Thanks in advance.
0xDD79757F.asc
On Mon, Sep 07, 2015 at 12:11:28AM -0600, Kenneth Freeman wrote:
> This may be a naïve question, but I've fired up my 64-bit Debian box now
> that the nights are cool, and editing the torrc to establish a bridge
> relay borks the browser. I provide anonymity much more than I use it
> myself, but
You might check for existing relays in their system.
This Robtex seems to have much of their network,
which they appear to lease from other providers:
https://www.robtex.com/en/advisory/dns/cr/crservers/
And while they advertise many network
blocks, it appears it's all slices
of just a few
Mega bits perhaps?
Mb rather than MB
8-)
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
This is curious: Appears a large number of Tor
client-bots have set
UseEntryGuards 0
>From current relays that have never had the guard flag:
extra-info moep DA8C1123CDB3ACD3B36CD7E7CEFBEA685DED2276
entry-ips us=360,de=296,fr=232,it=192,es=160,jp=104,ru=104,br=96,ir=96. . .
extra-info
https://www.torproject.org/docs/faq.html.en#UpgradeOrMove
I want to upgrade/move my relay. How do I keep the same key?
When upgrading your Tor relay, or running it on a different computer,
the important part is to keep the same identity key (stored in
"keys/secret_id_key" in your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm happy - my Tor relay says it's advertised bandwith is 1.1MB/s and
it is. Quote from Atlas:
Bandwidth rate: 1073.74 MB/s
Bandwidth burst: 2147.48 MB/s
Observed bandwidth: 1.11 MB/s
Hopefully if I can keep this up, I'll be qualifying for a shirt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I think so.
Also, is there a way to keep the fingerprint for my relay the same,
just in case I have to move computers? If so, what files do I have to
move?
On 07/09/2015 15:54, I wrote:
> Mega bits perhaps? Mb rather than MB 8-)
>
>
>
On 09/07/2015 01:07 PM, Kenneth Freeman wrote:
> On 09/07/2015 12:18 AM, Billy Humphreys wrote:
>> Well, people suggest that, unless you give <100KB/s, you should
>> run a relay, not a bridge, as more relays are used (and we have
>> Tor weather and such). You should be using Tor's daemon (apt-get
On 09/07/2015 12:25 AM, Roger Dingledine wrote:
> Well, it depends what you put in the torrc file. I assume you edited
> the torrc file that's inside the tor browser directory tree? Perhaps
> you did something there that it didn't like. Maybe you followed one of
> the instructions that
On 09/07/2015 12:18 AM, Billy Humphreys wrote:
> Well, people suggest that, unless you give <100KB/s, you should run a
> relay, not a bridge, as more relays are used (and we have Tor weather
> and such). You should be using Tor's daemon (apt-get install tor
> tor-arm) for the relay or bridge
On 09/07/2015 11:17 AM, Zack Weinberg wrote:
> On 09/07/2015 01:07 PM, Kenneth Freeman wrote:
>> On 09/07/2015 12:18 AM, Billy Humphreys wrote:
>>> Well, people suggest that, unless you give <100KB/s, you should
>>> run a relay, not a bridge, as more relays are used (and we have
>>> Tor weather
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
When I asked my reverse DNS to be added for my Tor exit relay, they
said that Tor nodes were disallowed due to the ToS, but didn't stop me.
I messaged back a few times (in normal UK time, 3AM over there) and I
got this reply:
'Hey there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
When I asked my reverse DNS to be added for my Tor exit relay, they
said that Tor nodes were disallowed due to the ToS, but didn't stop me.
I messaged back a few times (in normal UK time, 3AM over there) and I
got this reply:
'Hey there
On Wed, Aug 19, 2015 at 11:11:59AM -0400, starlight.201...@binnacle.cx wrote:
> So I'm left thinking that 95% or more of the
> bandwidth consumption and client count is from
> crusty old botnet bots running ancient versions
> of the Tor daemon.
Client count (for non guards), yes I think that's a
(The OSHER presentation is actually tomorrow. Duh!)
0xDD79757F.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
19 matches
Mail list logo
