Skip to content
Commits on Jan 13, 2016
Commits on Dec 13, 2015
  1. [test suite] start on %include_folder tests, make sure at least one v…

    …alid access.conf stanza has been parsed
Commits on Dec 12, 2015
Commits on Dec 10, 2015
Commits on Dec 9, 2015
Commits on Nov 18, 2015
Commits on Oct 31, 2015
Commits on Oct 20, 2015
Commits on Oct 18, 2015
Commits on Oct 14, 2015
Commits on Sep 5, 2015
  1. @damienstuart

    Updated c-unit-test README for changes in test locations. Updated aut…

    damienstuart committed
    …oconf files to remove references to the old c-unit-test configuration.
Commits on Aug 29, 2015
  1. @damienstuart
Commits on Aug 24, 2015
  1. [test suite] rm previous coverage files in coverage mode when --inclu…

    …de criteria is not used
Commits on Aug 19, 2015
  1. [build] add convenience script for ASan builds

    Sometimes when ASan support is wanted for fwknop, the following compile
    error can be generated. This script provides a means to solve this.
    fwknop-spa_comm.o: In function `send_spa_packet_http':
    /home/mbr/git/fwknop.git/client/spa_comm.c:516: undefined reference to `rpl_malloc'
    ../lib/.libs/ undefined reference to `rpl_realloc'
Commits on Jul 18, 2015
  1. [server] interface goes down will cause fwknopd to exit

    By default, fwknopd will now exit if the interface that it is
    sniffing goes down (patch contributed by Github user 'sgh7'). If this
    happens, it is expected that the native process monitoring feature in
    things like systemd or upstart will restart fwknopd. However, if fwknopd
    is not being monitored by systemd, upstart, or anything else, this
    behavior can be disabled with the EXIT_AT_INTF_DOWN variable in the
    fwknopd.conf file. If disabled, fwknopd will try to recover when a
    downed interface comes back up.
Commits on Jul 15, 2015
Commits on Jul 1, 2015
  1. add OS X ramdisk wrapper script

Commits on Jun 26, 2015
Commits on Jun 23, 2015
  1. [test suite] default to not zeroing profile coverage counters

        The typical work flow when generating gcov coverage results is:
    - compile fwknop with coverage support
    - run the test suite
    - hack on fwknop
    - re-run the test suite to see what coverage has been added
    This work flow is much more common than collecting coverage results
    for a complete test suite run. Therefore, this commit switches the
    default behavior in --enable-complete mode (which enables coverage
    support) to not zero-out coverage counters. A new argument
    --enable-profile-coverage-init zeros the counters in preparation
    for a global coverage run.
Commits on Jun 17, 2015
  1. add test/asan/ files

Commits on Jun 9, 2015
Commits on May 21, 2015
Commits on Apr 22, 2015
Commits on Apr 21, 2015
Commits on Apr 12, 2015
Commits on Apr 7, 2015
Commits on Mar 28, 2015
Something went wrong with that request. Please try again.