From: Eric Leblond <eric@inl.fr>
To: netfilter-devel@vger.kernel.org
Subject: [ULOGD PATCH 0/6] misc improvements and code cleaning
Date: Wed, 22 Sep 2010 02:47:16 +0200 [thread overview]
Message-ID: <1285116442-32490-1-git-send-email-eric@inl.fr> (raw)
Hi,
This patchset contains some light improvement and some code cleaning.
It starts with some build related fixes. The basic idea is to be able
to compile ulogd on a system without libnetfilter_conntrack and/or
libnetfilter_log installed:
- build: nfct and nflog can be disabled via configure option
- ulogd.conf: Comment library dependant plugins
Last build related patch adds a debug configure option to be able to
activate some debug related features (like being able to use gdb):
- build: add debug configure flag
Next significative patches are two code cleaning patches. The only thing
to note is that the second one could have some security implication:
- filter_MARK: code factorization.
- ulogd: use snprintf instead of sprintf in printpkt
If no one has problem with these patches, I will push them to the git
repository.
BR,
--
Eric Leblond <eric@inl.fr>
next reply other threads:[~2010-09-22 0:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 0:47 Eric Leblond [this message]
2010-09-22 0:47 ` [PATCH 1/6] build: nfct and nflog can be disabled via configure option Eric Leblond
2010-09-30 9:58 ` Pablo Neira Ayuso
2010-09-22 0:47 ` [PATCH 2/6] ulogd.conf: Comment library dependant plugins Eric Leblond
2010-09-30 9:51 ` Pablo Neira Ayuso
2010-09-30 21:23 ` Eric Leblond
2010-09-22 0:47 ` [PATCH 3/6] build: add debug configure flag Eric Leblond
2010-09-30 9:50 ` Pablo Neira Ayuso
2010-09-30 21:22 ` Eric Leblond
2010-10-01 22:22 ` Jan Engelhardt
2010-10-03 10:15 ` Pablo Neira Ayuso
2010-09-22 0:47 ` [PATCH 4/6] ulogd.conf: add a complex but useful stack example Eric Leblond
2010-09-22 0:47 ` [PATCH 5/6] filter_MARK: code factorization Eric Leblond
2010-09-22 0:47 ` [PATCH 6/6] ulogd: use snprintf instead of sprintf in printpkt Eric Leblond
2010-09-30 9:48 ` 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=1285116442-32490-1-git-send-email-eric@inl.fr \
--to=eric@inl.fr \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).