<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti/src/arti-example-config.toml, branch arti-v0.4.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-05-24T14:54:02Z</updated>
<entry>
<title>Make fs-mistrust configurable from the top level.</title>
<updated>2022-05-24T14:54:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-23T15:31:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b1fc4bd03bb4024cd5a467ccb682e88adf30bac7'/>
<id>urn:sha1:b1fc4bd03bb4024cd5a467ccb682e88adf30bac7</id>
<content type='text'>
This change requires a little refactoring of TorClientBuilder: now,
instead of enabling or disabling mistrust, it enables or disables
the decision to _override_ the mistrust in the config.
</content>
</entry>
<entry>
<title>arti-example-config.toml: Add a slightly improved comment</title>
<updated>2022-05-12T13:55:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-12T10:55:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cb42c01dd7e7e3666bd957333fed87b706033aca'/>
<id>urn:sha1:cb42c01dd7e7e3666bd957333fed87b706033aca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti-example-config.toml: Comment out all the example settings</title>
<updated>2022-05-12T13:55:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-12T13:48:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f18373a7d6e6566f416ee463cac207aabe3c9461'/>
<id>urn:sha1:f18373a7d6e6566f416ee463cac207aabe3c9461</id>
<content type='text'>
We expect that a user may copy this file and uses it as a starting
point for their own configuration.

When they do that, we don't want them to freeze the default config in
time.  Instead, we can expect them to uncomment settings they wish to
change.  Then when they upgrade arti, *other* settings will get the
new defaults, which I think is right.
</content>
</entry>
<entry>
<title>arti-example-config: Mark some non-default examples more clearly</title>
<updated>2022-05-12T13:55:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-12T13:48:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=85a310d7cc18d5940c2d6844c9282443d480059a'/>
<id>urn:sha1:85a310d7cc18d5940c2d6844c9282443d480059a</id>
<content type='text'>
Now,
  git-grep '^#[^ ]' crates/arti/src/arti-example-config.toml
has no ouptut.

This prepares us for the next commit.
</content>
</entry>
<entry>
<title>ARTI_EXAMPLE_CONFIG: Rename from ARTI_DEFAULTS</title>
<updated>2022-05-12T13:55:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-12T13:47:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8aab5a39968e8c99891720fcbfc4e3f1ce4cb0a5'/>
<id>urn:sha1:8aab5a39968e8c99891720fcbfc4e3f1ce4cb0a5</id>
<content type='text'>
The defaults are built into the code.  This is a doc-commented example
file, not the primary specification of what the defaults are.
</content>
</entry>
</feed>
