Skip to content

v1.5.0
Compare
Choose a tag to compare
@pcarana pcarana released this 10 Feb 18:00
v1.5.0
This tag was signed with the committer’s verified signature. The key has expired.
pcarana Francisco Javier Moreno
GPG key ID: 618A7AC16260CB01
Expired
Learn about vigilant mode.
f74278a
This commit was signed with the committer’s verified signature. The key has expired.
pcarana Francisco Javier Moreno
GPG key ID: 618A7AC16260CB01
Expired
Learn about vigilant mode.

The main updates of this release are:

  • Add argument to daemonize the process (--daemon arg).
  • Integrate TALs download to the binary (--init-tals arg).
  • Implement a thread pool for incoming RTR clients and TALs validation.

Special thanks to Ivaylo Josifov from VarnaIX/Varteh Ltd! For his contribution regarding the implementation of the thread pool.

The public key to verify the tarball is here (it isn't certified yet).

Changes since v1.4.2:

  • Updates

    • Add a warning message to the operation logs when the first validation cycle begins and ends. This is only to notify the RTR server availability to receive clients (router connections).
    • Add --daemon argument to daemonize FORT validator; fixes #25.
    • Integrate the TALs download to FORT binary, by using --init-tals argument.
    • Terminate execution when there's no more memory available, since a full recovery after this isn't assured; related to #40. The RPM and DEB packages will restart the service if FORT validator ends this way, this is achieved using RestartForceExitStatus service setting.
    • Implement a thread pool that's utilized to attend incoming RTR clients (see --thread-pool.server.max) and to process TALs during each validation cycle (see --thread-pool.validation.max).

  • Docs

Assets 6
Loading