lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1275040724.24490.121.camel@chilepepper> Date: Fri, 28 May 2010 12:58:44 +0300 From: Luciano Coelho <luciano.coelho@...ia.com> To: ext Jan Engelhardt <jengelh@...ozas.de> Cc: "netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "kaber@...sh.net" <kaber@...sh.net>, Timo Teras <timo.teras@....fi> Subject: Re: [RFC] netfilter: WIP: Xtables idletimer target implementation On Fri, 2010-05-28 at 10:05 +0200, ext Jan Engelhardt wrote: > On Friday 2010-05-28 07:25, Luciano Coelho wrote: > > > >Do you have any other suggestion on how I can associate the rules to > >specific interfaces? > > -A INPUT -i foo -j do > -A do -j idletimer > > A little funny, but actually this would allow me to keep a timer > for a group of interfaces rather than just per-if. Yes, this is what our userspace apps are doing. I've formulated my question in an unclear way. If you check the rest of the code, I create sysfs files under the interface's directory and use it as an attribute to notify the userspace when the timer has expired. In short, I need to figure out a way to associate each rule with an interface in sysfs, so I can notify the userspace when the timer has expired. I couldn't figure out another way to do it. Any suggestions? > >> >+static int xt_idletimer_checkentry(const struct xt_tgchk_param *par) > >> >+{ > >> >+ const struct xt_idletimer_info *info = par->targinfo; > >> >+ const struct ipt_entry *entryinfo = par->entryinfo; > >> >+ const struct ipt_ip *ip = &entryinfo->ip; > >> > >> I'm not sure spying on ipt_ip is a long-term viable solution. > > > >Do you have any other suggestions on how I could get an interface > >associated with the rule? I thought about having the userspace pass the > >interface as an option to the rule (like I already do for the timeout > >value), but that looked ugly to me, since the interface can already be > >defined as part of the ruleset. > > I have patches ready since a while that decouple ipt_ip > from a rule, so there is no guarantee that such will exist. Okay, if that's the case, then I don't know how to associate the rule with a specific net object in the kobject tree. Maybe I have to figure out a different way to notify the userspace, unless I add the target option I mentioned above. :/ -- Cheers, Luca. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists