The following scenario was noticed: If a node has a `rad/id` that is behind the one it is fetching from, where a delegate was added, then verification will fail since it will not fetch the new delegate -- if the scope is set to `Followed`. Irregardless if the `rad/id` is ahead or behind, the reference should be fetched to use as the delegates anchor since it will tell the fetching side which delegates in can fetch from the remote. If any of those delegates are missing then the remote is indeed lying. This is safe since the `refs/rad/id` reference is only updated by computing the COB rather than setting the OID, so it will not update through the fetch protocol itself. Signed-off-by: Fintan Halpenny <fintan.halpenny@gmail.com> X-Clacks-Overhead: GNU Terry Pratchett |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||