> On 24 Jan 2017, at 14:39, Kevin Beranek wrote:
>
>> Is the Address option set on this relay?
>
> Address is not set because it is generated from this template, which
> does not set Address:
> https://github.com/nusenu/ansible-relayor/blob/dev/templates/torrc.
To disable the warning, the temp
> Is the Address option set on this relay?
Address is not set because it is generated from this template, which
does not set Address:
https://github.com/nusenu/ansible-relayor/blob/dev/templates/torrc.
> Maybe we need to change this part of the warning:
>> If you have a static public IPv4 address
> On 24 Jan 2017, at 12:42, Kevin Beranek wrote:
>
> I can answer your questions because I'm the one that filed the issue
> previously referenced by nusenu.
>
>> What are the exact torrc lines?
>
> One relay where I see these log messages has a public address of
> 51.15.48.254 while the releva
> On 10 Jan 2017, at 09:17, teor wrote:
>
>> For example, maybe I want to use OnionShare to send my friend a 2GB
>> video clip, but anonymity doesn't matter to me. My friend and I already
>> know who each other are, and I'm not concerned about leaking what we're
>> doing, I just don't want to le
Hey George,
Thanks for sending this and summarizing everything!
> [D1] How to use version field:
>
> The version field is one byte long. If we use it as an integer we can
> encode 256 values in it; if we use it as a bitmap we could encode
> properties and such.
>
> My sugg
Hello George,
George Kadianakis wrote:
> Hello list,
>
> we've had discussions over the past years about how to encode prop224 onion
> addresses. Here is the latest thread:
> https://lists.torproject.org/pipermail/tor-dev/2016-December/011734.html
>
> Bikeshedding is over; it's time to finally
I can answer your questions because I'm the one that filed the issue
previously referenced by nusenu.
> What are the exact torrc lines?
One relay where I see these log messages has a public address of
51.15.48.254 while the relevant torrc lines are as follows:
ORPort 10.8.169.135:443
ORPort [200
> On 24 Jan 2017, at 00:36, George Kadianakis wrote:
...
> [D1.1] Default version value:
>
> The next question is what version value to assign to normal onion
> services. In the above scheme where:
>
> onion_address = base32(version + pubkey + checksum)
>
> the value of
Hi George,
George Kadianakis:
> What should we do in Tor? My suggestion is to use '\x98' as the default
> version value which prefixes all addresses with 't' (as in Tor). Check
> the examples I cited above.
>
> An alternative is to turn the scheme to:
> onion_addr
On 2017-01-23 07:50, George Kadianakis wrote:
George Kadianakis writes:
Hello list,
[D3] Do we like base32???
In this proposal I suggest we keep the base32 encoding since
we've been
using it for a while; but this is the perfect time to switch if
we feel
the need to.
George Kadianakis writes:
> Hello list,
>
>
>
> [D3] Do we like base32???
>
> In this proposal I suggest we keep the base32 encoding since we've been
> using it for a while; but this is the perfect time to switch if we feel
> the need to.
>
> For example, Bitcoin is using
On Mon, Jan 23, 2017 at 03:36:07PM +0200, George Kadianakis wrote:
> [D2] Checksum strength:
>
> In the suggested scheme we use a hash-based checksum of two bytes (16
> bits).
> This means that in case of an address typo, we have 1/65536 probability
> to not detect the error (fa
Hello list,
we've had discussions over the past years about how to encode prop224 onion
addresses. Here is the latest thread:
https://lists.torproject.org/pipermail/tor-dev/2016-December/011734.html
Bikeshedding is over; it's time to finally pick a scheme! My suggested scheme
basically follows f
Hi Tim,
Thank you for your insightful questions! My responses are below:
*> Is this the cheapest zone/region for computation or bandwidth? If I am
not in the US, would it be faster or cheaper for me to use a local google
data center?*
Yes, it would be faster for you to use a local google data ce
14 matches
Mail list logo
