mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
*	add semicolons if nothing returned	Daniel Eades	2021-11-25	1	-1/+1
\|
*	deglob some enums, use concise iteration syntax	Daniel Eades	2021-11-25	1	-6/+6
\|
*	tor-guardmgr: Add tests for a few functions.	Nick Mathewson	2021-11-02	1	-0/+39
\|
*	Mark primary guards as retriable when we come back online.	Nick Mathewson	2021-11-02	1	-0/+9
\| \| \| \| \| \| \| \| \| \| \| \|	We define "coming back online" as happening when a guard attempt succeeds, if that attempt that was launched when we seemed to be offline. We define "seeming to be offline" as having all of our primary guards marked unreachable, and having received no incoming network traffic in a while. Closes #216.
*	Add #[serde(flatten)] HashMap fields to serializable objects	eta	2021-10-27	1	-2/+12
\| \| \| \| \| \| \| \| \| \|	As per arti#175, we'd like to be able to handle newer Arti versions storing additional state in the persisted state files, without dropping this data on the floor when we write out changes to these files. Use the #[serde(flatten)] mechanism to achieve this, by adding catch-all HashMap<String, JsonValue> fields to all structs that are at risk of this happening to them.
*	Avoid a strange borrow syntax in tor_guardmgr::sample	Nick Mathewson	2021-10-26	1	-3/+3
\| \| \| \|	I'm not sure what I was thinking here.
*	Implement a "lightweight" form of pathbias detection.	Nick Mathewson	2021-10-26	1	-0/+10
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	We now track, for every guard: the total number of successful circuits we've built through it, along with the total number of "indeterminate" circuits. Recall that a circuit's status is "indeterminate" if it has failed for a reason that _might_ be the guard's fault, or might not be the guard's fault. For example, if extending to the second hop of the circuit fails, we have no way to know whether the guard deliberately refused to connect there, or whether the second hop is just offline. But we don't want to forgive all indeterminate circuit failures: if we did, then a malicious guard could simply reject any second hops that it didn't like, thereby filtering the client into a chosen set of circuits. As a stopgap solution, this patch now makes guards become permanently disabled if the fraction of their circuit failures becomes too high. See also general-purpose path bias selection (arti#65), and Mike's idea for changing the guard reachability definition (torspec#67). This patch doesn't do either of those. Closes #185.
*	guardmgr: Don't use guards that are marked as unlisted.	Nick Mathewson	2021-10-25	1	-7/+17
\| \| \| \|	Closes #202.
*	Implement the guard side of shared state directories.	Nick Mathewson	2021-10-21	1	-0/+9
\|
*	Make the guard selection function return a more useful type.	Nick Mathewson	2021-10-11	1	-0/+5
\|
*	Add a few tracing calls to tor-guardmgr.	Nick Mathewson	2021-10-08	1	-7/+20
\|
*	Resolve small issues and XXXX/TODO comments in GuardMgr.	Nick Mathewson	2021-10-07	1	-12/+17
\| \| \| \| \|	By the time I merge this, most of the comments should have tickets to go with them.
*	Tests for tor_guardmgr::sample.	Nick Mathewson	2021-10-07	1	-1/+330
\|
*	Initial backend implementation for guard node manager.	Nick Mathewson	2021-10-07	1	-0/+690
	There are some missing parts here (like persistence and tests) and some incorrect parts (I am 90% sure that the "exploratory circuit" flag is bogus). Also it is not integrated with the circuit manager code.