summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--changes/bug342993
-rw-r--r--changes/bug343035
-rw-r--r--doc/HACKING/CodingStandards.md7
-rw-r--r--doc/tor.1.txt4
-rw-r--r--src/core/or/circuitlist.c2
-rw-r--r--src/feature/client/entrynodes.c8
-rw-r--r--src/lib/crypt_ops/certs.md3
7 files changed, 24 insertions, 8 deletions
diff --git a/changes/bug34299 b/changes/bug34299
new file mode 100644
index 0000000000..464cf0d18a
--- /dev/null
+++ b/changes/bug34299
@@ -0,0 +1,3 @@
+ o Minor bugfixes (man page):
+ - Update the man page to reflect that MinUptimeHidServDirectoryV2
+ defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
diff --git a/changes/bug34303 b/changes/bug34303
new file mode 100644
index 0000000000..dce57f4646
--- /dev/null
+++ b/changes/bug34303
@@ -0,0 +1,5 @@
+ o Minor bugfixes (client performance):
+ - Resume being willing to use preemptively-built circuits when
+ UseEntryGuards is set to 0. We accidentally disabled this feature
+ with that config setting, leading to slower load times. Fixes bug
+ 34303; bugfix on 0.3.3.2-alpha.
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index a181759d60..99bc3e5022 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -193,8 +193,9 @@ Why use changes files instead of entries in the ChangeLog?
## Whitespace and C conformance
-Invoke `make check-spaces` from time to time, so it can tell you about
-deviations from our C whitespace style. Generally, we use:
+Tor's C code is written in accordance with the C99 standard. Invoke `make
+check-spaces` from time to time, so it can tell you about deviations from our C
+whitespace style. Generally, we use:
- Unix-style line endings
- K&R-style indentation
@@ -213,6 +214,8 @@ deviations from our C whitespace style. Generally, we use:
- Use `void foo(void)` to declare a function with no arguments. Saying
`void foo()` is C++ syntax.
- Use `const` for new APIs.
+ - Variables should be initialized when declared, rather than declared at the
+ top of a scope.
If you use an editor that has plugins for editorconfig.org, the file
`.editorconfig` will help you to conform this coding style.
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index 3dd7f5a64a..7b3150e2a4 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -3037,8 +3037,8 @@ on the public Tor network.
unreliable. (Default: 500)
[[MinUptimeHidServDirectoryV2]] **MinUptimeHidServDirectoryV2** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
- Minimum uptime of a v2 hidden service directory to be accepted as such by
- authoritative directories. (Default: 25 hours)
+ Minimum uptime of a relay to be accepted as a hidden service directory
+ by directory authorities. (Default: 96 hours)
[[RecommendedClientVersions]] **RecommendedClientVersions** __STRING__::
STRING is a comma-separated list of Tor versions currently believed to be
diff --git a/src/core/or/circuitlist.c b/src/core/or/circuitlist.c
index 4c37ef8b41..90cce47490 100644
--- a/src/core/or/circuitlist.c
+++ b/src/core/or/circuitlist.c
@@ -1943,7 +1943,7 @@ circuit_find_to_cannibalize(uint8_t purpose_to_produce, extend_info_t *info,
}
/* Ignore any circuits for which we can't use the Guard. It is possible
- * that the Guard was removed from the samepled set after the circuit
+ * that the Guard was removed from the sampled set after the circuit
* was created so avoid using it. */
if (!entry_guard_could_succeed(circ->guard_state)) {
goto next;
diff --git a/src/feature/client/entrynodes.c b/src/feature/client/entrynodes.c
index 55cc22cf0c..ded7db969a 100644
--- a/src/feature/client/entrynodes.c
+++ b/src/feature/client/entrynodes.c
@@ -3454,10 +3454,16 @@ entry_guards_update_state(or_state_t *state)
entry_guards_dirty = 0;
}
-/** Return true iff the circuit's guard can succeed that is can be used. */
+/** Return true iff the circuit's guard can succeed, that is, can be used. */
int
entry_guard_could_succeed(const circuit_guard_state_t *guard_state)
{
+ if (get_options()->UseEntryGuards == 0) {
+ /* we're fine with this circuit's first hop, because we're not
+ * configured to use entry guards. */
+ return 1;
+ }
+
if (!guard_state) {
return 0;
}
diff --git a/src/lib/crypt_ops/certs.md b/src/lib/crypt_ops/certs.md
index 2768548b2a..f3bd8c2c96 100644
--- a/src/lib/crypt_ops/certs.md
+++ b/src/lib/crypt_ops/certs.md
@@ -1,5 +1,5 @@
-@page certificates Certificates in Tor.
+@page certificates Certificates in Tor
We have, alas, several certificate types in Tor.
@@ -27,4 +27,3 @@ their associated keys.
documents that include keys and which are signed by keys. You can
consider these documents to be an additional kind of certificate if you
want.)
-