Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:44:57Zhttps://gitlab.torproject.org/legacy/trac/-/issues/31577make distcheck on macOS ignores --disable-asciidoc in its second configure in...2020-06-13T15:44:57Zteormake distcheck on macOS ignores --disable-asciidoc in its second configure invocationI build tor on macos using:
```
git clone https://git.torproject.org/tor.git
cd tor
mkdir build-c
../configure --disable-asciidoc --with-libevent-dir=/usr/local --with-openssl-dir=/usr/local/opt/openssl --enable-lzma --enable-zstd --enab...I build tor on macos using:
```
git clone https://git.torproject.org/tor.git
cd tor
mkdir build-c
../configure --disable-asciidoc --with-libevent-dir=/usr/local --with-openssl-dir=/usr/local/opt/openssl --enable-lzma --enable-zstd --enable-libscrypt CC=clang --enable-gcc-warnings --enable-expensive-hardening
make distcheck
```
Which fails with:
```
checking whether the compiler accepts @warning_flags... yes
==================================
Building Tor has failed since manpages cannot be built.
You need asciidoc installed to be able to build the manpages.
To build without manpages, use the --disable-asciidoc argument
when calling configure.
==================================
make: *** [distcheck] Error 1
Exit 2
```
What am I doing wrong?
Does "make distcheck" support a build directory inside tor/ ?Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/15775Add IPv4 Fallback Directory List to tor, active by default2020-06-13T14:51:37ZteorAdd IPv4 Fallback Directory List to tor, active by defaultweasel writes on tor-dev:
Tor has included a feature to fetch the initial consensus from nodes
other than the authorities for a while now. We just haven't shipped a
list of alternate locations for clients to go to yet.
Reasons why we ...weasel writes on tor-dev:
Tor has included a feature to fetch the initial consensus from nodes
other than the authorities for a while now. We just haven't shipped a
list of alternate locations for clients to go to yet.
Reasons why we might want to ship tor with a list of additional places
where clients can find the consensus is that it makes authority
reachability and BW less important.
At the last Tor dev meeting we came up with a list of arbitrary
requirements that nodes should meet to be included in this list.
We want them to have been around and using their current key, address,
and port for a while now (120 days), and have been running, a guard, and
a v2 directory mirror for most of that time.
I have written a script to come up with a list of notes that match our
criteria. It's currently at
https://www.palfrader.org/volatile/fallback-dir/get-fallback-dir-candidates
It currently produces
https://www.palfrader.org/volatile/2015-04-17-VjBkc8DWV8c/list
See https://lists.torproject.org/pipermail/tor-dev/2015-April/008674.html
This file current has 329 entries, and takes up approximately 32kB.
If we hard-coded it in the binary like the authorities, it would increase the binary size by approximately 2% on my platform.
Edit: nickm favours putting it in `torrc.defaults`
Edit 2: weasel notes `torrc.defaults` is for package maintainers. Putting it in a list of strings in the code. Much like the authorities.
Do we expect this in by 0.2.7?
Edit: Yes
Do we want to work on a signed file first (#15774)?
(A signed file needs a well-defined threat model and signature verification has to work without access to the authorities or fallback directories.)
Edit: No clear threat model, defer.Tor: 0.2.8.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/15228Identify candidates for FallbackDir, and ship with a list of them2020-06-13T14:45:50ZNick MathewsonIdentify candidates for FallbackDir, and ship with a list of themBack long ago, we added a feature to allow torrc to list a bunch of FallbackDir entries. These tell a client where to look for consensus directory documents, so that the clients don't just load the authorities down.
It would be good if...Back long ago, we added a feature to allow torrc to list a bunch of FallbackDir entries. These tell a client where to look for consensus directory documents, so that the clients don't just load the authorities down.
It would be good if we shipped with such a list.
One idea has been to identify directories that have:
* a stable IP:Port over a long time,
* reasonably good uptime (as a fraction)
* good bandwidth
* a contact address.
Then, contact the admins of these directory caches and ask them for permission to put them on a list.
(See also #8374)Tor: 0.2.8.x-finalteorteor