From: Florian Boelstler <euphoria@web.de>
To: netfilter@lists.netfilter.org
Subject: Handling incoming DCC session
Date: Wed, 02 Jun 2004 00:55:55 +0200 [thread overview]
Message-ID: <40BD097B.60709@web.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
a long time ago someone posted a patch for 2.4.18 kernels [1], which
allowed incoming DCCs get caught by a default 'related' rule.
As far as I know this patch wasn't applied by the module maintainer.
Unfortunately the sources have changed in the meantime and the patch
doesn't work anymore.
I was trying to adapt the patch to kernel 2.6.5. But I don't have enough
knowledge to successfully modife it.
Is there anybody out there who owns a patch for 2.6.x series?
Thanks for your help!
Florian
[1]
http://lists.netfilter.org/pipermail/netfilter-devel/2002-July/008665.html
- --
Public PGP key is available on common key servers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAvQl7wT2gPfZm6tURAv2eAKCyXR+3FBzZX4qlm8em5EiJfBCthACeIOYI
N2YuqzKk0chg8VAanrTbp9g=
=JXtM
-----END PGP SIGNATURE-----
reply other threads:[~2004-06-01 22:55 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=40BD097B.60709@web.de \
--to=euphoria@web.de \
--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