Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Sep 4, 2012
  1. another merge from master

    authored
  2. bump version to 2.0.3

    authored
Commits on Sep 1, 2012
  1. merged master 2.0.3 changes

    authored
Commits on Aug 30, 2012
  1. file permissions and client buffer overflow fix

    authored
    - [client+server] Fernando Arnaboldi from IOActive found that strict
    filesystem permissions for various fwknop files are not verified.  Added
    warnings whenever permissions are not strict enough, and ensured that
    files created by the fwknop client and server are only set to user
    read/write.
    - [client] Fernando Arnaboldi from IOActive found a local buffer overflow
    in --last processing with a maliciously constructed ~/.fwknop.run file.
    This has been fixed with proper validation of .fwknop.run arguments.
Commits on Aug 18, 2012
  1. fwknop-2.0.2 release

    authored
  2. merged from master

    authored
Commits on Aug 15, 2012
Commits on Aug 11, 2012
Commits on Aug 5, 2012
Commits on Aug 4, 2012
  1. bumped version to 2.0.2-pre1

    authored
Commits on Jul 24, 2012
  1. bumped version to fwknop-2.0.1

    authored
Commits on Jul 15, 2012
  1. @damienstuart
Commits on Jul 13, 2012
Commits on Jul 10, 2012
  1. bumped version to 2.0.1-pre2

    authored
Commits on Jul 9, 2012
  1. bumped version to 2.0.1-pre1

    authored
Commits on Jun 15, 2012
  1. Test suite support for function coverage testing via gcov

    authored
    Added --enable-profile-coverage to the configure script to have the fwknop
    binaries compiled with gcc profiling support in order to see which functions
    get executed by the test suite via gcov.  The last test executed by the test
    suite under --enable-profile-coverage contains all fwknop functions that
    were not executed under the test run (function execution totals are
    cumlative).
Commits on Jan 2, 2012
  1. added FKO_CHECK_COMPILER_ARG_LDFLAGS_ONLY to fix ro-relocations and i…

    authored
    …mmediate binding protection compliation warnings on FreeBSD
Commits on Dec 29, 2011
  1. @damienstuart

    Refactored configure.ac to use a custom macro for compiler flag checks.

    damienstuart authored Damien S. Stuart committed
    Set version to 2.0 (non-release candidate).
    Minor typo fixes.
Commits on Dec 6, 2011
Commits on Sep 9, 2011
  1. Added read-only relocations and immediate bindings

    authored
    Commit 4248b26 removed read-only relocations
    and immediate bindings for FreeBSD systems (and the same was done for OpenBSD
    systems too).  This commit adds these security features back in as linker
    options by only changing LDFLAGS as opposed to also adding the corresponding
    flags to CFLAGS.  The end result is that the following errors are fixed:
    
    gcc: -z: linker input file unused because linking not done
    gcc: relro: linker input file unused because linking not done
Commits on Aug 27, 2011
  1. PF support on OpenBSD in progress, fwknop --fw-list now works

    authored
    This is the first commit that has fwknopd interact with the PF firewall on
    OpenBSD (via fwknopd --fw-list to show any active fwknopd rules).
Commits on Aug 25, 2011
  1. Added autoconf check for pf firewalls

    authored
    On OpenBSD systems fwknop now checks for pf firewalls via autoconf.  The next
    step will be to fill in support for pf via the C code.
  2. Disabled read-only relocations and immediate binding compiler protect…

    authored
    …ions
    
    Similarly to FreeBSD systems, gcc throws the following warnings with read-only
    relcations and immediate binding protections - disbabled for now:
    
    gcc: -z: linker input file unused because linking not done
    gcc: relro: linker input file unused because linking not done
    gcc: -z: linker input file unused because linking not done
    gcc: now: linker input file unused because linking not done
Commits on Aug 21, 2011
  1. bumped version to 2.0.0rc4

    authored
  2. On FreeBSD, made gpgme header path inclusion optional

    authored
    If gpgme is installed on FreeBSD systems it appears that
    -I/usr/local/include/gpgme must be added to the include path, but this change
    only adds the path if gpgme is installed and going to be used.
Commits on Aug 20, 2011
  1. Fixed a few minor compiler warnings on FreeBSD

    authored
    This commit fixes a few warnings about possible uninitialized and unused
    variables.
  2. On FreeBSD disable read-only relocations and immediate binding protec…

    authored
    …tions
    
    gcc on FreeBSD generates the following errors when the -Wl,-z,relro -Wl,-z,now
    flags are used:
    
    gcc: -z: linker input file unused because linking not done
    gcc: relro: linker input file unused because linking not done
    gcc: -z: linker input file unused because linking not done
    gcc: now: linker input file unused because linking not done
  3. Added -Wall for all gcc warnings during compile

    authored
    Enable gcc compilation to include -Wall for all warnings (can be disabled
    with --disable-wall to ./configure).
  4. Bug fix for ./configure args to disable compile time security options

    authored
    The ./configure script would generate the following error for the attempted
    use of the --without-stackprotector (and other related options like
    --without-pie):
    
    configure: WARNING: unrecognized options: --without-stackprotect
Commits on Aug 18, 2011
  1. Added stack protection, PIE, fortify source, etc.

    authored
    Added various security options that can be enabled at compile time.  These
    options include everything that the "hardening-check" script written by Kees
    Cook checks for.  After this change, the hardening-check script produces the
    following output against the fwknopd binary:
    
    $ hardening-check server/.libs/fwknopd
    server/.libs/fwknopd:
     Position Independent Executable: yes
     Stack protected: yes
     Fortify Source functions: yes
     Read-only relocations: yes
     Immediate binding: yes
    
    One of the compile outputs (for example) that shows the new options is:
    
    /bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..     -g -O2 -fstack-protector-all -fPIE -pie -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -MT fko_decode.lo -MD -MP -MF .deps/fko_decode.Tpo -c -o fko_decode.lo fko_decode.c
    
    From the hardening-check man page, here is a description of each of these
    options:
    
    NAME
           hardening-check - check binaries for security hardening features
    
    SYNOPSIS
           Examine a given set of ELF binaries and check for several security
           hardening features, failing if they are not all found.
    
    DESCRIPTION
           This utility checks a given list of ELF binaries for several security
           hardening features that can be compiled into an executable.  These
           features are:
    
           Position Independent Executable
                   This indicates that the executable was built in such a way
                   (PIE) that the "text" section of the program can be relocated
                   in memory.  To take full advantage of this feature, the
                   executing kernel must support text Address Space Layout
                   Randomization (ASLR).
    
           Stack Protected
                   This indicates that the executable was compiled with the
                   gcc(1) option -fstack-protector.  The program will be
                   resistant to have its stack overflowed.
    
           Fortify Source functions
                   This indicates that the executable was compiled with
                   -D_FORTIFY_SOURCE=2 and -O2 or higher.  This causes certain
                   unsafe glibc functions with their safer counterparts (e.g.
                   strncpy instead of strcpy).
    
           Read-only relocations
                   This indicates that the executable was build with -Wl,-z,relro
                   to have ELF markings (RELRO) that ask the runtime linker to
                   mark any regions of the relocation table as "read-only" if
                   they were resolved before execution begins.  This reduces the
                   possible areas of memory in a program that can be used by an
                   attacker that performs a successful memory corruption exploit.
    
           Immediate binding
                   This indicates that the executable was built with -Wl,-z,now
                   to have ELF markings (BIND_NOW) that ask the runtime linker to
                   resolve all relocations before starting program execution.
                   When combined with RELRO above, this further reduces the
                   regions of memory available to memory corruption attacks.
Commits on Aug 11, 2011
  1. Added autoconf support for non-dbm file cache.

    authored
    This change starts on support for a simple file-based cache mechanism
    for tracking SPA digests.  This removes the libgdbm/libndbm dependency
    by default, but it can be re-enabled with the --disable-file-cache
    argument to the ./configure script.
Something went wrong with that request. Please try again.