From: Patrick McHardy <kaber@trash.net>
To: KOVACS Krisztian <hidden@sch.bme.hu>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [NETFILTER 2/5]: Fix potential memory corruption in NAT code (aka memory NAT)
Date: Fri, 22 Jul 2005 10:09:56 +0200 [thread overview]
Message-ID: <42E0A9D4.405@trash.net> (raw)
In-Reply-To: <1122018440.1098.3.camel@nienna.balabit>
KOVACS Krisztian schrieb:
> Hi,
>
> Sometimes netfilter-devel seems to be a write-only list...
>
> http://lists.netfilter.org/pipermail/netfilter-devel/2004-March/014412.html
Indeed, sorry for that. Next time just press us a bit harder please :)
Regards
Patrick
next prev parent reply other threads:[~2005-07-22 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 7:35 [NETFILTER 2/5]: Fix potential memory corruption in NAT code (aka memory NAT) Patrick McHardy
2005-07-22 7:47 ` KOVACS Krisztian
2005-07-22 8:09 ` Patrick McHardy [this message]
2005-07-22 19:50 ` David S. Miller
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=42E0A9D4.405@trash.net \
--to=kaber@trash.net \
--cc=hidden@sch.bme.hu \
--cc=netfilter-devel@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 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.