From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter@vger.kernel.org
Cc: netfilter-announce@lists.netfilter.org,
netfilter-devel@vger.kernel.org, lwn@lwn.net
Subject: [ANNOUNCE] libnetfilter_log 0.0.15 release
Date: Fri, 15 Aug 2008 22:24:43 +0200 [thread overview]
Message-ID: <48A5E60B.2000306@netfilter.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi!
The netfilter project proudly presents:
* libnetfilter_log-0.0.15
libnetfilter_log is a userspace library providing interface to packets
that have been logged by the kernel packet filter. It is is part of a
system that deprecates the old syslog/dmesg based packet logging. See
ChangeLog for more details.
You can download them from:
http://www.netfilter.org
ftp://ftp.netfilter.org
Enjoy,
Pablo - on behalf of the Netfilter Project.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
[-- Attachment #2: ChangeLog --]
[-- Type: text/plain, Size: 172 bytes --]
Eric Leblond (1):
Add parsing function for raw hardware header
Pablo Neira Ayuso (2):
conditional compilation of testsuite utils
bump version to 0.0.15
reply other threads:[~2008-08-15 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48A5E60B.2000306@netfilter.org \
--to=pablo@netfilter.org \
--cc=lwn@lwn.net \
--cc=netfilter-announce@lists.netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.