BSD Ports

net/fort 1.7.0 FreeBSD

FORT Validator is an open source RPKI validator

System
FreeBSD
Repository
FreeBSD ports
Maintainer
[email protected]
Last update
Commit
fc30167e01
License
MIT
Categories
net
Package size
173.4 KiB, 450.9 KiB installed

Description

FORT validator is an MIT-licensed RPKI Relying Party, this is a tool offered as part of the FORT project. It is a solution that allows operators to validate BGP routing information against the RPKI repository for use in router configuration and resolution. The service performs the validation of the entire RPKI repository, and which serves the resulting ROAs for easy access by your routers.

In the other systems

SystemPortVersion
FreeBSDnet/fort1.7.0
OpenBSDnet/fort1.6.8p0
DragonFlynet/fort1.6.6

Install

Binary package:

pkg install fort

From the ports tree:

cd /usr/ports/net/fort/ && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	fort>0:net/fort

Packages

The version each package repository carries. “-” means the repository builds no package of it, “n/a” that there is no such repository.

Repositoryaarch64amd64armv6armv7i386
FreeBSD:14:latest1.7.01.7.01.5.3_31.6.6_11.7.0
FreeBSD:14:quarterly1.7.01.7.0n/a1.6.6_11.7.0
FreeBSD:15:latest1.7.01.7.0n/a1.6.6_11.6.6_1
FreeBSD:15:quarterly1.7.01.7.0n/an/an/a
FreeBSD:16:latest1.7.01.7.0n/an/an/a
FreeBSD:16:quarterlyn/an/an/an/an/a

Dependencies

As this port's Makefile names them.

Library 3

Runtime 1

The full lists below include those, and their dependencies in turn.

Build dependencies 22
Run dependencies 24

No port depends on this one.

Configuration

No options to configure.

USES
gnome localbase:ldflags pkgconfig ssl
Service scripts
fort

Message after installing

A default configuration file has been installed in
/usr/local/etc/fort/fort-config.json.sample.

To use FORT, you will need the Trust Anchor Locator (TAL) files.
You can download these by running "fort --init-tals" as follows:

# fort --init-tals --tal /usr/local/etc/fort/tal

When you have downloaded the TAL files, you can start the RTR
server and validator:

# sysrc fort_enable=YES # or edit /etc/rc.conf manually
# service fort start

The default configuration will bind the RTR server to localhost
on port 8323.

Consult the FORT manual for more information:
https://nicmx.github.io/FORT-validator/run.html

Files

Manual pages 1
  • fort(8)
pkg-plist 5
  • bin/fort
  • share/man/man8/fort.8.gz
  • @dir etc/fort/repository
  • @dir etc/fort/tal
  • @sample etc/fort/fort-config.json.sample
distinfo 1
FileSizeSHA256
fort-1.7.0.experimental.tar.gz51932870075f82effe5cf9752b13463f50c4379fdf93e5c28bdf6cba04e9621e2288cc
Master sites 1
  • https://github.com/NICMx/FORT-validator/releases/download/${DISTVERSIONFULL}/

Commit history 2

DateCommitCreditsLog message
fc30167e01 Philip Paeps net/fort: fix fetching 1.7.0.experimental
Reported by: pkg-fallout Fixes: 4839e2b8d102 ("net/fort: Update to 1.7.0.experimental") MFH: 2026Q3 Pointy hat to: philip
4839e2b8d1 Philip Paeps net/fort: Update to 1.7.0.experimental
- Update to 1.7.0.experimental - Changelog: https://github.com/NICMx/FORT-validator/releases/tag/1.7.0.experimental Please note that max-rtr-version defaults to zero. This is because Fort's validation currently yields no router keys (defeating the purpose of RTRv1), and the RTRv2 specification is still receiving updates. The latter is all the ".experimental" suffix refers to. If you raise max-rtr-version to 2, you'll be trying a feature that hasn't been RFC'd yet. MFH: 2026Q3