===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
fort-validator-1.4.2/docs/routers.md-27-- [`--server.address`](usage.html#--serveraddress): network address where the server will listen for routers.
fort-validator-1.4.2/docs/routers.md:28:- [`--server.port`](usage.html#--serverport): port or service (see `‘$ man services’`) where the server will listen for routers.
fort-validator-1.4.2/docs/routers.md-29-- [`--server.backlog`](usage.html#--serverbacklog): max number of outstanding connections in the server listen queue.
##############################################
fort-validator-1.4.2/docs/run.md-89-
fort-validator-1.4.2/docs/run.md:90:> ![img/warn.svg](img/warn.svg) This quirk applies to glibc, you can check if your OS has it by running (from a command line): `$ ldd --version`
fort-validator-1.4.2/docs/run.md-91-
##############################################
fort-validator-1.4.2/docs/usage.md-309-
fort-validator-1.4.2/docs/usage.md:310:If this field is omitted, Fort will attempt to bind the server using the IP address `INADDR_ANY` (for an IPv4 address) or `IN6ADDR_ANY_INIT` (for an IPv6 address); see '`$ man getaddrinfo`'.
fort-validator-1.4.2/docs/usage.md-311-
##############################################
fort-validator-1.4.2/docs/usage.md-319-
fort-validator-1.4.2/docs/usage.md:320:This is a string because a service alias can be used as a valid value. The available aliases are commonly located at `/etc/services`. (See '`$ man services`'.)
fort-validator-1.4.2/docs/usage.md-321-
##############################################
fort-validator-1.4.2/docs/usage.md-671-Useful when the CA from the peer isn't located at the default OS certificate bundle. If specified, the peer certificate will be verified using the CAs at the path. The directory MUST be prepared using the `rehash` utility from the SSL library:
fort-validator-1.4.2/docs/usage.md:672:- OpenSSL command (with help): `$ openssl rehash -h`
fort-validator-1.4.2/docs/usage.md:673:- LibreSSL command (with help): `$ openssl certhash -h`
fort-validator-1.4.2/docs/usage.md-674-
##############################################
fort-validator-1.4.2/docs/usage.md-949->
fort-validator-1.4.2/docs/usage.md:950:> e.g. `$ make FORT_FLAGS='-DENABLE_STRICT_STRATEGY'`
fort-validator-1.4.2/docs/usage.md-951-
##############################################
fort-validator-1.4.2/docs/usage.md-1017-- **Availability:** JSON only
fort-validator-1.4.2/docs/usage.md:1018:- **Default:** `[ "--recursive", "--delete", "--times", "--contimeout=20", "--timeout=15", "$REMOTE", "$LOCAL" ]`
fort-validator-1.4.2/docs/usage.md-1019-
##############################################
fort-validator-1.4.2/docs/usage.md-1021-
fort-validator-1.4.2/docs/usage.md:1022:Fort will replace `"$REMOTE"` with the remote URL it needs to download, and `"$LOCAL"` with the target local directory where the file is supposed to be dropped.
fort-validator-1.4.2/docs/usage.md-1023-
##############################################
fort-validator-1.4.2/docs/usage.md-1027-- **Availability:** JSON only
fort-validator-1.4.2/docs/usage.md:1028:- **Default:** `[ "--times", "--contimeout=20", "--timeout=15", "--dirs", "$REMOTE", "$LOCAL" ]`
fort-validator-1.4.2/docs/usage.md-1029-
##############################################
fort-validator-1.4.2/docs/usage.md-1031-
fort-validator-1.4.2/docs/usage.md:1032:Fort will replace `"$REMOTE"` with the remote URL it needs to download, and `"$LOCAL"` with the target local directory where the file is supposed to be dropped.
fort-validator-1.4.2/docs/usage.md-1033-
##############################################
fort-validator-1.4.2/fort_setup.sh-54-exit_on_err "$# -gt 0" 'Usage: '"$0"' TALS_PATH.\nTALS_PATH must be an existent directory path.'
fort-validator-1.4.2/fort_setup.sh:55:TMP=`echo "$1"`
fort-validator-1.4.2/fort_setup.sh-56-if ! [ -d "$TMP" ] ; then
##############################################
fort-validator-1.4.2/src/clients.c-85-int
fort-validator-1.4.2/src/clients.c:86:clients_get_addr(int fd, struct sockaddr_storage *addr)
fort-validator-1.4.2/src/clients.c-87-{
##############################################
fort-validator-1.4.2/src/clients.h-33-int clients_get_min_serial(serial_t *);
fort-validator-1.4.2/src/clients.h:34:int clients_get_addr(int, struct sockaddr_storage *);
fort-validator-1.4.2/src/clients.h-35-
##############################################
fort-validator-1.4.2/src/rtr/pdu.c-263-	    || read_int8(reader, &pdu->zero)
fort-validator-1.4.2/src/rtr/pdu.c:264:	    || read_in_addr(reader, &pdu->ipv4_prefix)
fort-validator-1.4.2/src/rtr/pdu.c-265-	    || read_int32(reader, &pdu->asn);
##############################################
fort-validator-1.4.2/src/rtr/pdu.c-277-	    || read_int8(reader, &pdu->zero)
fort-validator-1.4.2/src/rtr/pdu.c:278:	    || read_in6_addr(reader, &pdu->ipv6_prefix)
fort-validator-1.4.2/src/rtr/pdu.c-279-	    || read_int32(reader, &pdu->asn);
##############################################
fort-validator-1.4.2/src/rtr/pdu_serializer.c-59-	ptr = write_int8(ptr, pdu->zero);
fort-validator-1.4.2/src/rtr/pdu_serializer.c:60:	ptr = write_in_addr(ptr, pdu->ipv4_prefix);
fort-validator-1.4.2/src/rtr/pdu_serializer.c-61-	ptr = write_int32(ptr, pdu->asn);
##############################################
fort-validator-1.4.2/src/rtr/pdu_serializer.c-79-	ptr = write_int8(ptr, pdu->zero);
fort-validator-1.4.2/src/rtr/pdu_serializer.c:80:	ptr = write_in6_addr(ptr, pdu->ipv6_prefix);
fort-validator-1.4.2/src/rtr/pdu_serializer.c-81-	ptr = write_int32(ptr, pdu->asn);
##############################################
fort-validator-1.4.2/src/rtr/primitive_reader.c-112-int
fort-validator-1.4.2/src/rtr/primitive_reader.c:113:read_in_addr(struct pdu_reader *reader, struct in_addr *result)
fort-validator-1.4.2/src/rtr/primitive_reader.c-114-{
##############################################
fort-validator-1.4.2/src/rtr/primitive_reader.c-118-int
fort-validator-1.4.2/src/rtr/primitive_reader.c:119:read_in6_addr(struct pdu_reader *reader, struct in6_addr *result)
fort-validator-1.4.2/src/rtr/primitive_reader.c-120-{
##############################################
fort-validator-1.4.2/src/rtr/primitive_reader.h-21-int read_int32(struct pdu_reader *, uint32_t *);
fort-validator-1.4.2/src/rtr/primitive_reader.h:22:int read_in_addr(struct pdu_reader *, struct in_addr *);
fort-validator-1.4.2/src/rtr/primitive_reader.h:23:int read_in6_addr(struct pdu_reader *, struct in6_addr *);
fort-validator-1.4.2/src/rtr/primitive_reader.h-24-int read_string(struct pdu_reader *, uint32_t, rtr_char **);
##############################################
fort-validator-1.4.2/src/rtr/primitive_writer.c-30-unsigned char *
fort-validator-1.4.2/src/rtr/primitive_writer.c:31:write_in_addr(unsigned char *buf, struct in_addr value)
fort-validator-1.4.2/src/rtr/primitive_writer.c-32-{
##############################################
fort-validator-1.4.2/src/rtr/primitive_writer.c-36-unsigned char *
fort-validator-1.4.2/src/rtr/primitive_writer.c:37:write_in6_addr(unsigned char *buf, struct in6_addr value)
fort-validator-1.4.2/src/rtr/primitive_writer.c-38-{
##############################################
fort-validator-1.4.2/src/rtr/primitive_writer.h-8-unsigned char *write_int32(unsigned char *, uint32_t);
fort-validator-1.4.2/src/rtr/primitive_writer.h:9:unsigned char *write_in_addr(unsigned char *, struct in_addr);
fort-validator-1.4.2/src/rtr/primitive_writer.h:10:unsigned char *write_in6_addr(unsigned char *, struct in6_addr);
fort-validator-1.4.2/src/rtr/primitive_writer.h-11-
##############################################
fort-validator-1.4.2/src/rtr/rtr.c-387-
fort-validator-1.4.2/src/rtr/rtr.c:388:	addr_str = (clients_get_addr(fd, &sockaddr) == 0)
fort-validator-1.4.2/src/rtr/rtr.c-389-	    ? sockaddr2str(&sockaddr, buffer)
##############################################
fort-validator-1.4.2/src/rtr/rtr.c-402-static void
fort-validator-1.4.2/src/rtr/rtr.c:403:print_client_addr(struct sockaddr_storage *addr, char const *action, int fd)
fort-validator-1.4.2/src/rtr/rtr.c-404-{
##############################################
fort-validator-1.4.2/src/rtr/rtr.c-441-
fort-validator-1.4.2/src/rtr/rtr.c:442:	print_client_addr(&param.addr, "closed", param.fd);
fort-validator-1.4.2/src/rtr/rtr.c-443-	end_client(param.fd);
##############################################
fort-validator-1.4.2/src/rtr/rtr.c-528-
fort-validator-1.4.2/src/rtr/rtr.c:529:			print_client_addr(&client_addr, "accepted", client_fd);
fort-validator-1.4.2/src/rtr/rtr.c-530-
##############################################
fort-validator-1.4.2/src/rtr/rtr.c-571-	end_client(client->fd);
fort-validator-1.4.2/src/rtr/rtr.c:572:	print_client_addr(&(client->addr), "terminated", client->fd);
fort-validator-1.4.2/src/rtr/rtr.c-573-	/* Don't call clients_forget to avoid deadlock! */