* [PATCH 0/3] change TCP protoinfo via netlink
@ 2005-08-25 20:42 Pablo Neira
0 siblings, 0 replies; only message in thread
From: Pablo Neira @ 2005-08-25 20:42 UTC (permalink / raw)
To: Netfilter Development Mailinglist; +Cc: Harald Welte, Patrick McHardy
Taken from [1]:
I think that users must be able to set the TCP state of a conntrack,
otherwise if they create a conntrack via libnfnetlink_conntrack, the
state will be set to NONE. If users aren't able to set the state, I'd
consider that the library is kind of incomplete. I don't like the idea
of kidding with stuff that could be compromising either, but I don't
want to lose any features. So, I think that the solution is *remark* in
the documentation of libnfnetlink_conntrack and the conntrack manpage
that changing the protocol private information like the state could
result in problems, I'll to do such thing.
[1]https://lists.netfilter.org/pipermail/netfilter-devel/2005-August/020784.html
@Harald: I've reworked the patches as you suggested.
--
Pablo
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-08-25 20:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-25 20:42 [PATCH 0/3] change TCP protoinfo via netlink Pablo Neira
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.