-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Daniel!
Thank you so much for your immediate, detailed and informative answer.
I really like the example you offered as it clearly illustrates the
parsing order.
Your answer is very helpful for me to decide where I should place the
%include line
> On 3 Jul 2017, at 06:02, s7r wrote:
>
> George Kadianakis wrote:
>> Hello,
>>
>> here is some background information and summarizing of proposal 247
>> "Defending Against Guard Discovery Attacks using Vanguards" for people
>> who plan to work on this in the short-term future.
>>
>
> Hello,
George Kadianakis wrote:
> Hello,
>
> here is some background information and summarizing of proposal 247
> "Defending Against Guard Discovery Attacks using Vanguards" for people
> who plan to work on this in the short-term future.
>
Hello,
I have discussed in Amsterdam briefly with David about
Hello iry,
The precedence for tor options is the following (1 overrides 2, etc...):
1. Command line options.
2. Configuration file options (your /etc/torrc).
3. Defaults file options (your /usr/share/tor/tor-service-defaults-torrc).
In the same file, options that appear later override earlier op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello, Tor developers!
With the implementation of torrc.d, there will be at least two Tor
config files and one Tor config directory by default in Debian tor
package. However, I am not able to find the documents on what the
parsing order Tor follows.
