aboutsummaryrefslogtreecommitdiff
path: root/crates/arti/src/arti-example-config.toml
Commit message (Collapse)AuthorAgeFilesLines
* Fix typosDimitris Apostolou2023-07-221-6/+6
|
* arti cfg tests: Add keystore to example config.Gabriela Moldovan2023-07-131-0/+20
| | | | Closes #939
* arti config: Remove extraneous whitespace.Gabriela Moldovan2023-07-131-5/+5
|
* arti: Add a `logging.time_granularity` option with 1s default.Nick Mathewson2023-07-061-0/+16
| | | | | | | This lets us provide less information in our logs: in particular, it lets us avoid logging with microsecond precision. Closes #551.
* Turn off HS client connections by defaultIan Jackson2023-06-291-1/+10
| | | | As per IRC discussion, re lack of Vanguards.
* HS configuration: Add retry parameters to configurationIan Jackson2023-06-281-0/+6
| | | | | | | I think these should go in `[circuit_timing]`. That section already has some retry parameters, so is not strictly *timing*. This is not honoured yet.
* HS configuration: Add and honour `allow_onion_addrs` in configurationIan Jackson2023-06-281-0/+3
| | | | | | | We put this in `[address_filter]`. The interaction with the corresponding stream preference is a bit complicated. We must turn the stream pref into a `BoolOrAuto`.
* tor-ptmgr: make configuration use builders, plumb into arti-clienteta2022-11-161-0/+16
| | | | | | | This brings the draft configuration mechanisms in tor-ptmgr in line with the config in other crates, using builders. It also plumbs the config type through into the main `arti-client` config, and adds some example lines to `arti-example-config.toml`.
* bridge config: Clarify that examples are nonfunctionalIan Jackson2022-10-121-0/+2
|
* bridges config example: Add much more example syntaxIan Jackson2022-10-121-4/+14
|
* bridges config example: Add bridges section to example configIan Jackson2022-10-121-0/+21
| | | | | | | This is precisely the text from the original version of !744. There is no implementation yet, so we must add a entry to the exception list in the tests.
* arti: cfg: Rename `*_port` to `*_listen` and change the typeIan Jackson2022-08-251-2/+2
| | | | | | | This commit largely follows the example for resolve_alternative_specs. The difference is that there are two fields, so we use a macro to avoid recapitulating the field names.
* arti: Raise the default console log severity to "info"Nick Mathewson2022-08-251-1/+1
| | | | | Previously we logged at "debug", but that's not meant to user-facing.
* arti: Do not allow running as root.Nick Mathewson2022-08-241-0/+6
| | | | | | This can be overridden with `application.allow_running_as_root`. Part of #523.
* channel: Introduce padding configIan Jackson2022-08-161-1/+13
| | | | | Nothing actually reads this yet, and we also want a client-global default for padding.
* Introduce ChannelConfigIan Jackson2022-08-161-0/+4
| | | | | This commit is just the necessary plumbing. The config is currently empty. We'll add something to it, for padding control, later.
* arti: Add support for process hardeningNick Mathewson2022-08-151-0/+9
| | | | | | | | | | | | | This is a compile-time feature with an associated configuration flag, both enabled by default. When it's turned on, hardening prevents the arti process from dumping core or being attached to by low-privileged processes. (This is a defense-in-depth measure, not an absolute way to prevent attacks. For more information, see [`secmem_proc`](https://docs.rs/secmem-proc/0.1.1/secmem_proc/).) Closes #364.
* Rename download_tolerance to directory_toleranceNick Mathewson2022-07-221-2/+5
| | | | Closes #503.
* Add a configuration option for reachable_addrsNick Mathewson2022-06-171-0/+10
| | | | (This doesn't do anything yet.)
* mistrust: Canonicalise prefix from Some("") to NoneIan Jackson2022-05-301-0/+1
| | | | | This allows us to add the proper default example to the arti example config file.
* arti: config: Canonicalise ports, and provide example dns_portIan Jackson2022-05-301-0/+3
| | | | | | | | | | | | | Now the validated configuration will never be `Some(0)`, even if that is what was written in the config file. The arti CLI parser can still produce this, so we don't touch the code that actually uses this. (Without the canonicalisation the default builder produces `None` for the `dns_port`, but the example would produce `Some(0)`, which is semantically identical but fails the test.) See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some background.
* config: Provide tor_config::resolve_option and resolve journaldIan Jackson2022-05-301-2/+2
| | | | | | | | | | | | | | Canonicalise the `logging.journald` setting in the validated configuration. Now it will never be `Some("")`, even if that is what was written in the config file. This allows us to write `journald = ""` in the example configuration. (Without the canonicalisation the default builder produces `None` and the example would produce `Some("")`, which are semantically identical but fail the test.) See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some background.
* arti: config example: Add entries for tor_network fieldsIan Jackson2022-05-301-0/+9
| | | | | These weren't previously discussed. It's not practical or useful to show the actual default values here.
* arti: config example: Add some missing defaultsIan Jackson2022-05-301-3/+17
| | | | Found by my forthcoming test.
* arti: example config: Arrange to uncomment logfilesIan Jackson2022-05-301-2/+2
| | | | | This makes the config default parser see just "[ ]", an empty list, which is indeed the default.
* Make fs-mistrust configurable from the top level.Nick Mathewson2022-05-241-0/+24
| | | | | | 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.
* arti-example-config.toml: Add a slightly improved commentIan Jackson2022-05-121-0/+1
|
* arti-example-config.toml: Comment out all the example settingsIan Jackson2022-05-121-24/+24
| | | | | | | | | | 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.
* arti-example-config: Mark some non-default examples more clearlyIan Jackson2022-05-121-10/+11
| | | | | | | | Now, git-grep '^#[^ ]' crates/arti/src/arti-example-config.toml has no ouptut. This prepares us for the next commit.
* ARTI_EXAMPLE_CONFIG: Rename from ARTI_DEFAULTSIan Jackson2022-05-121-0/+183
The defaults are built into the code. This is a doc-commented example file, not the primary specification of what the defaults are.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 20:00:46 +0000