Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

See also ticket 31654.

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

Here we make it clear we're only looking at listable variable names,
not at whether the variables themselves are gettable.

Also, remove an extraneous h.

(This commit is not a fixup, because of rebase conflicts.)

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

(This option tests our existing behavior, not necessarily the most
sensible behavior.)

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

The old names remain as #defines that cause variables to get one or
more flags.

Now every flag-testing function in confparse.c tests exactly one flag.

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

Since the flags are now stored with compatible numbering, we can
just OR them together and see whether the flag we want is in the
result.

(Net code removal!)

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

Using a bitfield here will enable us to unify the var_type_def_t flags
with the config_var_t flags.

(This commit does not yet do that unification, and does not yet
rename or refactor any flags.  It only changes booleans into bits.)

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

Previously they checked the individual flags inside var_type_def_t;
now they call the appropriate var_type_is_*() functions.

(These functions will be removed entirely by the end of this branch.)

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

Don't use "derived" directly, but check its implications for listing
and copying.

Nick Mathewson authored 5 years ago and David Goulet committed 5 years ago

We had though to make all obsolete and invisible variables
ungettable, so that GETCONF would reject them.  But it turns out
that this isn't the current behavior of GETCONF with those
variables.  So for now, I'm leaving the current behavior unchanged.
(See ticket 31647 for a proposal to change the behavior.)

Part of 31615.

Merged modified lines from bug31615_041, and unmodified lines
from master.

Part of 31615.

Merged modified lines from bug31615_040, and unmodified lines
from maint-0.4.1.

These levels get out of date really easily: we'll implement a level
dump command in tor in 31614.

They also cause conflicts and inconsistencies when merging forward
level changes.

Part of 31615.

Closes #31673

David Goulet authored 5 years ago and Nick Mathewson committed 5 years ago

Signed-off-by: David Goulet <dgoulet@torproject.org>

David Goulet authored 5 years ago and Nick Mathewson committed 5 years ago

Move it outside of the validation function since 0 is a valid value but
disables defenses.

Signed-off-by: David Goulet <dgoulet@torproject.org>

David Goulet authored 5 years ago and Nick Mathewson committed 5 years ago

Signed-off-by: David Goulet <dgoulet@torproject.org>

Fix levels for subsystems that depend on log/err
* winprocess (security) doesn't use err:
  * call windows process security APIs as early as possible
  * init err after winprocess
  * move wallclock so it's still after err
* network and time depend on log:
  * make sure that network and time can use logging.
  * init network and time after log

Add comments explaining the module init order.

Fixes bug 31615; bugfix on 0.4.0.1-alpha.