From: Gervasio Bernal <gervasiobernal@speedy.com.ar>
To: Pablo Neira <pablo@eurodev.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: New target: can't delete rule
Date: Mon, 12 Sep 2005 19:23:36 +0000 [thread overview]
Message-ID: <1126553016.15667.0.camel@Pentium> (raw)
In-Reply-To: <431F6A0E.1090707@eurodev.net>
El mié, 07-09-2005 a las 22:30, Pablo Neira escribió:
> Gervasio Bernal wrote:
> > I'm from Argentina and I'm developing a new target for iptables with a
> > college friend. This new target uses the Linux Cryptographic API.
> >
> > We are debbuging the new extension and we noticed a rare behavior.
> > First we inserted the rule like this:
> > #iptables -t mangle -A INPUT -s xxx.xxx.xxx.xxx -j NEW --param hello
> > And we don't have problems.
> >
> > The problem appears when we tried to erase the rule:
> > #iptables -t mangle -D INPUT -s xxx.xxx.xxx.xxx -j NEW --param hello
> > It says: :-(
> > iptables: No chain/target/match by that name
> >
> > But, if we put this:
> > #iptables -t mangle -D INPUT 1
> > It erases correctly :-)
> >
> > Why it works with a method and not with the another one?
> > It can be because we allocating memory in checkentry function and
> > freeing it in destroy function?
> > How can we correct this rare behavior?
>
> I bet that you have a pointer in the private info section of the target.
> See that iptables sets that pointer to NULL at rule creation.
> Afterwards, once checkentry() is called, such pointer won't be NULL anymore.
>
> At removal, the rule built by iptables sets that pointer to NULL. Such
> rule will be compared with the ruleset hold in kernel space but no
> matches will be found since the pointers mismatch.
>
> This problem is well known and it's very easy to fix up (look for
> userspacesize and offsetof in iptables/extensions). See ipt_limit,
> ipt_CLUSTERIP...
>
> But it's *even* easier to figure out what's wrong with yout module if
> you post it here, in the mailing list.
>
> --
> Pablo
>
Pablo:
I did what you said, but I cannot make walk it.
This is my libipt_CRYPT.c
static struct iptables_target CRYPT
= {
.name = "CRYPT",
.version = IPTABLES_VERSION,
.size = IPT_ALIGN(sizeof(struct ipt_CRYPT_info)),
.userspacesize = offsetof(struct ipt_CRYPT_info,
table_alloc_ptr),
.help = &help,
.init = &init,
.parse = &parse,
.final_check = &final_check,
.print = &print,
.save = &save,
.extra_opts = opts
};
This is my ipt_CRYPT.h
struct ipt_CRYPT_info
{
char key[MAX_KEY_SIZE];
unsigned int block_size;
unsigned int key_size;
struct tabla_alloc* table_alloc_ptr;
};
struct tabla_alloc
{
struct crypto_tfm *tfm;
struct tabla_alloc* next;
struct tabla_alloc* ant;
};
Greetings
next prev parent reply other threads:[~2005-09-12 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 18:09 New target: can't delete rule Gervasio Bernal
2005-09-07 22:30 ` Pablo Neira
2005-09-07 22:34 ` Patrick McHardy
2005-09-07 23:58 ` Pablo Neira
2005-09-12 19:23 ` Gervasio Bernal [this message]
2005-09-12 23:24 ` Pablo Neira
2005-09-12 20:45 ` Gervasio Bernal
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=1126553016.15667.0.camel@Pentium \
--to=gervasiobernal@speedy.com.ar \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
/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.