ipt_recent needs a maintainer!

[Juergen Kreileder]

Hi,

> ipt_recent was merged into the mainline kernel quite some time ago, but
> unfortunately the original author doesn't seem to be compelled to
> maintain it.  There's nothing wrong with that, after all we do this
> voluntarily!  But we have to deal with the consequences.
> 
> Some people from the netfilter community have indicated that it's coding
> style rectifies a re-write, but that's something I don't want to address
> now.
> 
> What we need as a short-term solution is somebody maintaining this
> beast, somebody looking into bug reports, etc.

I'm using ipt_recent, so I'm interested in keeping it in shape.
I'm familiar with the code and its current issues (see
http://blog.blackdown.de/2005/05/09/fixing-the-ipt_recent-netfilter-module/)

So I'd like to volunteer for maintaining it.

> There are a number of bug reports coming in, and nobody really takes
> care of them.  The latest one seems to be
> https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=415

This is exactly the bug described on my site.

> but there are more, like
> https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=369

That bug is fixed since 2.6.12. The code in earlier kernels wasn't
64-bit safe.


	Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://blog.blackdown.de/