List view
Interim release before 2.7.0 to tie off a few loose ends and fix a few bugs.
Overdue by 9 year(s)•Due by November 30, 2016•1/6 issues closedRelease fwknop-2.9.0 with support for: - Optional pthreads support - this should be an optional feature gated by autoconf #defines, and not enabled by default. For users that want this, it would make for a cleaner way to implement firewall rules on the server side. - User interfaces: GNOME, KDE, Windows. Implement viable user interfaces for SPA packet creation. - Ruby bindings for libfko - extend interpreted language support to Ruby. - ipfw NAT support - extend fwknopd's NAT capabilities into the ipfw world.
Overdue by 7 year(s)•Due by November 30, 2017•2/4 issues closedFor the 2.8.0 release the main things to be included are: - Full IPv6 support - While updating the client to send SPA packets over IPv6 will be relatively easy and some code has already been included for this, the fwknopd side will be harder. - SELinux + AppArmor policy support - both SELinux and AppArmor implement a Mandatory Access Control (MAC) layer within the kernel, and the fwknop sources should include policies to leverage these tools. - See what we can do for GPG support on Windows and other platforms (Android). This one may be a long shot.
Overdue by 8 year(s)•Due by May 31, 2017•1/5 issues closedFor the 2.7 release here are the main things that will be included in this release: - Privilege separation support - only two areas of fwknopd need to run as root: packet acquisition and firewall rule adjustment. Everything else should run as non-privileged user. - libcap-ng support. libcap-ng provides a way to drop privileges for certain operations, and fwknopd should support this. - OpenBSD PF NAT support - extend fwknopd's NAT capabilities into the PF world. - Optional OpenSSL direct usage for crypto operations
Overdue by 8 year(s)•Due by March 31, 2017•9/23 issues closed