From: pcarana <pc.moreno2099@gmail.com>
Date: Tue, 8 Oct 2019 17:18:12 +0000 (-0500)
Subject: Merge branch rtrv1
X-Git-Tag: v1.1.0~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=54588a128e8fa157b123c5cfca4e8beacc963b45;p=thirdparty%2FFORT-validator.git

Merge branch rtrv1
---

54588a128e8fa157b123c5cfca4e8beacc963b45
diff --cc README.md
index 1b31e298,0f55acea..356f8c24
--- a/README.md
+++ b/README.md
@@@ -1,59 -1,9 +1,9 @@@
- # FORT
+ # FORT Validator
  
- An RPKI Validator and RTR Server.
+ An RPKI Validator and RTR Server, part of the [FORT project](https://www.fortproject.net).
  
- ## Installation
+ ## Documentation
  
- Dependencies:
+ FORT Validator's documentation (installation, usage, etc.) can be found at [https://nicmx.github.io/FORT-validator/](https://nicmx.github.io/FORT-validator/).
  
- 1. libcrypto ([LibreSSL](http://www.libressl.org/) or [OpenSSL](https://www.openssl.org/) >= 1.1)
- 2. [jansson](https://github.com/akheron/jansson)
- 3. [rsync](http://rsync.samba.org/)
- 
- The validator is currently supported in *64-bit* OS. A 32-bit OS may face the [Year 2038 problem](https://en.wikipedia.org/wiki/Year_2038_problem) when handling dates at certificates.
- 
- After all the dependencies are installed, run:
- 
- ```
- ./autogen.sh
- ./configure
- make
- make install
- ```
- 
- More documentation at [https://nicmx.github.io/FORT-validator/](https://nicmx.github.io/FORT-validator/).
- 
- ## Usage
- 
- Use the following command to run an RTR server that will serve the ROAs resulting from a validation rooted at the trust anchors defined by the TALs contained at directory `--tal`:
- 
- ```
- fort \
- 	--tal <path to your TAL files> \
- 	--local-repository <path where you want to keep your local cache> \
- 	--server.address <your intended RTR server address> \
- 	--server.port <your intended RTR server port>
- ```
- 
- Run Fort validator as standalone (perform validation and exit) and print ROAs to CSV file:
- 
- ```
- fort \
- 	--mode standalone \
- 	--output.roa <path to output file in CSV format> \
- 	--tal <path to your TAL files> \
- 	--local-repository <path where you want to keep your local cache>
- ```
- 
- Run Fort validator using a [SLURM file](https://tools.ietf.org/html/rfc8416):
- 
- ```
- fort \
- 	--slurm <path to a SLURM file> \
- 	--tal <path to your TAL files> \
- 	--local-repository <path where you want to keep your local cache> \
- 	--server.address <your intended RTR server address> \
- 	--server.port <your intended RTR server port>
- ```
- 
- Visit the [Usage](https://nicmx.github.io/FORT-validator/doc/usage.html) section at the docs to know all the possible Fort configurations, these are some usage examples.
 -If you wish to generate the docs by yourself, visit the [docs directory](https://github.com/NICMx/FORT-validator/tree/master/docs).
++If you wish to generate the docs by yourself, visit the [docs directory](https://github.com/NICMx/FORT-validator/tree/master/docs).
diff --cc docs/index.md
index 1c19062f,ea96b992..327837dd
--- a/docs/index.md
+++ b/docs/index.md
@@@ -10,4 -10,4 +10,4 @@@ FORT validator is an MIT-licensed RPKI 
  
  ## Status
  
- Version [{{ site.fort-latest-version }}](https://github.com/NICMx/FORT-validator/releases/tag/v{{ site.fort-latest-version }}){:target="_blank"} is the first official release! Don't forget to read the [docs](doc/index.html).
 -Version [{{ site.fort-latest-version }}](https://github.com/NICMx/FORT-validator/releases/tag/v{{ site.fort-latest-version }}){:target="_blank"} is the latest official release, includes RTR version 1 support and a considerable improvement in execution time.
++Version [{{ site.fort-latest-version }}](https://github.com/NICMx/FORT-validator/releases/tag/v{{ site.fort-latest-version }}){:target="_blank"} is the latest official release, includes RTR version 1 support and a considerable improvement in execution time.