Re: [tor-dev] Proposal: only parse .torrc files in torrc.d directory

> On 4 Feb 2018, at 15:04, iry wrote: > >>> Therefore, may I propose to let Tor parse only the files whose >>> name ends with .torrc ? >> >> Yes, this is standard behaviour among many tools. To be more precise, most tools accept files ending in ".conf". We might want tor to

Re: [tor-dev] Proposal: only parse .torrc files in torrc.d directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 >> Therefore, may I propose to let Tor parse only the files whose >> name ends with .torrc ? > > Yes, this is standard behaviour among many tools. > >> Or maybe even only parse number_filename.torrc for better >> consistency and for more clear

Re: [tor-dev] Proposal: only parse .torrc files in torrc.d directory

> On 4 Feb 2018, at 09:37, iry wrote: > > In best case users will just be frustrated because Tor does not work > as expected and in worst case this could be dangerous. This could be a > severe problem especially because of the following reasons: > 1. filename.torrc~

[tor-dev] Proposal: only parse .torrc files in torrc.d directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Tor Developers, I have been testing and using the torrc.d feature for a while, and here is a potential improvement we may make. Currently, when using a torrc.d directory, for example: > %include /etc/torrc.d/ Every file in the directory will

Re: [tor-dev] No Control Socket when DisableNetwork 1

> My first suggestion would be > [...] > My second suggestion would be to get a Tor binary and run it yourself, > not as part of a package. If it works there, then you know that your > next steps are to figure out why your package isn't working for you Hi Yawning and Roger! Thank you so much

Re: [tor-dev] small fixes for the sources.list generator (and new options)

nusenu: > If someone with commit privileges has time to review and merge > before the weekend that would be great. teor marked the ticket as merge_ready on 2018-01-31, does anyone with commit privileges have time to merge it? https://trac.torproject.org/projects/tor/ticket/25107 thanks,

Re: [tor-dev] onionoo.tpo stuck at 2018-02-02 19:00

Karsten Loesing: > On 2018-02-03 12:53, nusenu wrote: >> >> >> Karsten Loesing: >>> On 2018-02-03 01:32, nusenu wrote: thanks for looking into it >>> >>> Looks like the CollecTor host is down, along with several other hosts. I >>> sent mail to the admins. >> >> Does that imply that we are

Re: [tor-dev] onionoo.tpo stuck at 2018-02-02 19:00

On 2018-02-03 12:53, nusenu wrote: > > > Karsten Loesing: >> On 2018-02-03 01:32, nusenu wrote: >>> thanks for looking into it >> >> Looks like the CollecTor host is down, along with several other hosts. I >> sent mail to the admins. > > Does that imply that we are actually loosing raw

Re: [tor-dev] onionoo.tpo stuck at 2018-02-02 19:00

Karsten Loesing: > On 2018-02-03 01:32, nusenu wrote: >> thanks for looking into it > > Looks like the CollecTor host is down, along with several other hosts. I > sent mail to the admins. Does that imply that we are actually loosing raw CollecTor data until it comes back? --

Re: [tor-dev] Starting with contributing to Anonymous Local Count Statistics.

Hi, On 02/02/18 12:08, Jaskaran Singh wrote: > Also, the Metrics team has(?) to come up with a proposal on this IIRC. > Until then it would not be considered a valid project? Considered a valid project by whom? Metrics is currently very busy and may not have time to assist with the project, but

Re: [tor-dev] onionoo.tpo stuck at 2018-02-02 19:00

On 2018-02-03 01:32, nusenu wrote: > thanks for looking into it Looks like the CollecTor host is down, along with several other hosts. I sent mail to the admins. All the best, Karsten ___ tor-dev mailing list tor-dev@lists.torproject.org