diff options
Diffstat (limited to 'doc/09.RPKI.RP.HierarchicalRsync.md')
| -rw-r--r-- | doc/09.RPKI.RP.HierarchicalRsync.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/09.RPKI.RP.HierarchicalRsync.md b/doc/09.RPKI.RP.HierarchicalRsync.md index d996379c..196f0d2d 100644 --- a/doc/09.RPKI.RP.HierarchicalRsync.md +++ b/doc/09.RPKI.RP.HierarchicalRsync.md @@ -11,10 +11,10 @@ Note The relying parties in this configuration still perform their own validation, they just let the gatherers do the work of collecting the unvalidated data for them. A gatherer in a configuration like this would look just like a stand-alone -relying party as discussed above. The only real difference is that a gatherer -must also make its unauthenticated data collection available to other relying -parties. Assuming the standard configuration, this will be the directory -`/var/rcynic/data/unauthenticated` and its subdirectories. +relying party as discussed [above][HierarchicalRsync]. The only real difference is that a +gatherer must also make its unauthenticated data collection available to other +relying parties. Assuming the standard configuration, this will be the +directory `/var/rcynic/data/unauthenticated` and its subdirectories. There are two slightly different ways to do this with rsync: @@ -84,3 +84,5 @@ Configuration for such a module would look like: transfer logging = yes path = /var/rcynic/data/unauthenticated comment = Unauthenticated RPKI data + +[HierarchicalRsync]: 09.RPKI.RP.HierarchicalRsync.md |