Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-announce@lists.netfilter.org,
	netfilter <netfilter@lists.netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Cc: lwn@lwn.net
Subject: [ANNOUNCE] Release of libnfnetlink, libnfnetlink_conntrack and libnetfilter_queue
Date: Thu, 11 Jan 2007 01:58:59 +0100	[thread overview]
Message-ID: <45A58BD3.1010000@netfilter.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

Hi!

The netfilter project proudly presents:

	libnfnetlink-0.0.25
	libnfnetlink_conntrack-0.0.50
	libnetfilter_queue-0.0.13

libnfnetlink
	is the low-level userspace library for nfnetlink based
	communication between the kernel-side netfilter and the
	userspace world.

libnfnetlink_conntrack
	is the library for userspace access to the in-kernel connection
	tracking table.

libnetfilter_queue
	is the library to filter and mangle packets from userspace

You can download the three releases from
	http://www.netfilter.org/projects/libnfnetlink/files/libnfnetlink-0.0.25.tar.bz2
http://www.netfilter.org/projects/libnetfilter_conntrack/files/libnetfilter_conntrack-0.0.50.tar.bz2

http://www.netfilter.org/projects/libnetfilter_queue/files/libnetfilter_queue-0.0.13.tar.bz2

Attached to this email the changelog. Upgrade is recommended.

Happy firewalling,

	Pablo Neira Ayuso (for the Netfilter Project)

p.s: the signature verification can complain about the key expiration
date, sorry for that, we are still in the process of the renewal.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

[-- Attachment #2: ChangeLog --]
[-- Type: text/plain, Size: 1020 bytes --]

libnfnetlink 0.0.25
======================================================================

Changes from 0.0.16:

- Add iterator API
	[ Pablo Neira ]

- Add replacements for nfnl_listen and nfnl_talk
	[ Pablo Neira ]

- Fix error handling
	[ Pablo Neira ]

- Add assertions
	[ Pablo Neira ]

- Add documentation
	[ Pablo Neira ]

- Minor cleanups
	[ Pablo Neira ]

- Initialize callback structure
	[ Victor Stinner ]

libnetfilter_conntrack 0.0.50
======================================================================

Changes from 0.0.31:

- Introduce new API and documentation
	[ Pablo Neira ]

- Fix minor nitpick in the XML output
	[ Victor Stinner ]

- Minor fix in the counters parsing
	[ Pablo Neira ]

- Implement getter for the ATTR_USE attribute
	[ Victor Stinner ]

- ATTR_*_COUNTER_*, ATTR_USE and ATTR_ID are unsettable
	[ Victor Stinner ]

libnetfilter_queue 0.0.13
======================================================================

Changes from 0.0.12:

- Set maximum queue length
	[ Eric Leblond ]

             reply	other threads:[~2007-01-11  0:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11  0:58 Pablo Neira Ayuso [this message]
2007-01-11 14:51 ` [ANNOUNCE] Release of libnfnetlink, libnfnetlink_conntrack and libnetfilter_queue TheGesus
2007-01-11 15:42   ` Pablo Neira Ayuso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45A58BD3.1010000@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=lwn@lwn.net \
    --cc=netfilter-announce@lists.netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox