arbitary length matchinfo

arbitary length matchinfo

[Juha Heljoranta]

Is it possible to create arbitary length matchinfo? I couldn't find any
info on this.

What I want is an path:

	struct ipt_foo_info {
		char *path;
	}

maximum path length in Linux is 4096 and doing

	struct ipt_foo_info {
		char path[4096];
	}

is bit crazy.

Regards,
Juha Heljoranta

Re: arbitary length matchinfo

[Henrik Nordstrom]

On Fri, 15 Apr 2005, Juha Heljoranta wrote:

> Is it possible to create arbitary length matchinfo?

Not without modifying both libiptc and the kernel. The structures does 
support this, but libiptc assumes the matchinfo is of fixed size, and the 
kernel also verifies the size is the expected size.

> What I want is an path:

Just curious: why?

Regards
Henrik

Re: arbitary length matchinfo

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

On Fri, Apr 15, 2005 at 02:32:08PM +0300, Juha Heljoranta wrote:
> Is it possible to create arbitary length matchinfo? I couldn't find any
> info on this.

no.
 
> What I want is an path:
> 
> 	struct ipt_foo_info {
> 		char *path;
> 	}
> 
> maximum path length in Linux is 4096 and doing

you definitely don't want filename paths in an iptables rule.  this is
insane ;)

-- 
- Harald Welte <laforge@netfilter.org>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]