Hi,

Le vendredi 27 octobre 2006 à 15:53 +0200, Pablo Neira Ayuso a écrit :
> Eric Leblond wrote:
> > What's the status of this new API ? Current status of
> > libnetfilter_conntrack code is really disappointing.
> 
> Indeed, you can blame me for that. I'm working on the new API that I'll 
> try to release asap. I'm going to put this in my high priority queue.

That's good news !

> 
> > We at INL are currently working on using libnetfilter_conntrack to
> > provide tools for firewall administrators. The first one
> > pynetfilter_conntrack is already available and a web management
> > interface will soon be released. By doing this we are trying to improve
> > the usability of this new system.
> 
> I'd like to see your python binding in the libnetfilter_conntrack tree 
> but I have to fix some stuff before, please consider that this would 
> require some extra work from your part.

No problem. We really think it's the correct place for this code and it
will worth the work to put it there.

> 
> > We are doing this because we think the new features provided by
> > libnetfilter_conntrack really improve a lot the way we use and "live"
> > with a Netfilter firewall.
>
> I already commented what my intentions are: add more new API, do not 
> remove the old one but mark it as deprecated, strongly recommend people 
> to move to the new API. The deprecated API will be removed after quite 
> some time.

Is it possible to introduce a version number of the API in a #define to
be able to do some conditional compilations ?

BR,
-- 
Eric Leblond <eric@inl.fr>
INL