All of lore.kernel.org
 help / color / mirror / Atom feed
* RE: Request: Submission of Rulesets
@ 2005-08-25 11:56 Derick Anderson
  2005-08-25 14:35 ` Thomas Jones
  0 siblings, 1 reply; 8+ messages in thread
From: Derick Anderson @ 2005-08-25 11:56 UTC (permalink / raw)
  To: netfilter

 
Out of curiosity (and the lack of fully understanding your intent), how
would this DTD validate a ruleset? I imagine you'd be trying to go
beyond syntax since netfilter will tell you when you do something silly
like a --dport without a -p tcp|udp anyway. If that's so, what is your
standard for failure of a ruleset? Or success of a ruleset? I can submit
a working ruleset that isn't optimal (accepting RELATED,ESTABLISHED
connections as the last rule, for example) or that checks src/dst IPs
but not which interface...

Admittedly I don't know that much about XML and DTDs. I don't know how
powerful DTDs can be, but it seems to me like you'd need a high-level
programming language in order to test for more than syntactical
correctness. A simulation environment for Netfilter rules is something
I'd really like to see.

Derick Anderson


> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org 
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of 
> Thomas Jones
> Sent: Wednesday, August 24, 2005 6:48 PM
> To: netfilter@lists.netfilter.org
> Subject: Re: Request: Submission of Rulesets
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday 24 August 2005 17:36, /dev/rob0 wrote:
> >
> > If I could remember the URL I would post it.
> >
> 
> If you find it forward it to me. Sounds like it could be an 
> interesting trick or two.
> 
> >
> > Ah, *that* was the piece I was missing. You are accepting 
> the rulesets 
> > submitted as valid (probably) and are simply using them to 
> test your 
> > DTD. Is that it? I thought you were compiling it from the submitted 
> > rulesets, and that, I guess we agree, is not possible.
> >
> 
> Some of the targets and matches located in the extra 
> repository have not been introduced. These will definitely 
> take some work. Altough progress has been made, I am sure 
> that I have neglected various syntactical portions of the 
> netfilter framework.
> 
> >
> > I still don't, but at least the gibberish issue is cleared up. :)
> 
> Fair enough. ;)
> 
> Cheers,
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFDDPlAoR5cE1e/kEIRAnTvAJ9MdKaDz6DME9g7XQRhK9ZfCHq8fQCcDQJq
> Y9zJBZ5HNohUBV8e0eg/D7Y=
> =h+/H
> -----END PGP SIGNATURE-----
> 
> 


^ permalink raw reply	[flat|nested] 8+ messages in thread
* RE: Request: Submission of Rulesets
@ 2005-08-26 11:57 Derick Anderson
  0 siblings, 0 replies; 8+ messages in thread
From: Derick Anderson @ 2005-08-26 11:57 UTC (permalink / raw)
  To: Thomas Jones, netfilter

  
What you said made sense regarding DTDs and XSL stylesheets. XML (from
what I know of it) is a great standard.

> > I can submit
> > a working ruleset that isn't optimal (accepting RELATED,ESTABLISHED 
> > connections as the last rule, for example) or that checks 
> src/dst IPs 
> > but not which interface...
> 
> I am not here to judge yourself or the logical purpose of 
> your rules. I simply want to contribute to the community. 
> None of my projects are for profit. 
> However, I do think that it could be a good starting point 
> for new users to the netfilter framework to be able to 
> construct valid rules and/or rulesets.

My point there wasn't to say "I'm going to try and mess up your
project", it was an example of what I was asking about earlier -
evaluation of a ruleset that goes beyond correct syntax. I'll be
rebuilding my company's iptables firewall soon (the previous sys-admin
didn't quite grasp stateful inspection or using least privilege) and so
perhaps I'll submit a copy with external IPs obfuscated. 

I think there's a lot of work that can be done to ease the learning
curve for Netfilter. It took me a year to fully understand the basics -
where I knew what would happen to a particular packet as it traversed
the chains. A project like yours combined with a simulation environment
would have saved me a lot of dropped SSH sessions. =) I've got no
problem helping out.
 
> > Admittedly I don't know that much about XML and DTDs. I 
> don't know how 
> > powerful DTDs can be, but it seems to me like you'd need a 
> high-level 
> > programming language in order to test for more than syntactical 
> > correctness.
> 
> That is a totally different beast. This is where the XSL 
> stylesheets come into play.
> 
> > A simulation environment for Netfilter rules is something 
> I'd really 
> > like to see.
> 
> Agreed. Construction of pseudo datagrams and testing for 
> resultant outcomes would be a very interesting project. 
> 
> Cheers,
> Thomas

Derick Anderson

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFDDddIoR5cE1e/kEIRAqn0AKDc0iJETnOHYDBWOQlekweswOj3sQCeIo/6
> LhSsuJbNwjqcG9fSmV5Hw2U=
> =0+PB
> -----END PGP SIGNATURE-----
> 


^ permalink raw reply	[flat|nested] 8+ messages in thread
* Request: Submission of Rulesets
@ 2005-08-24 18:14 Thomas Jones
  2005-08-24 21:07 ` /dev/rob0
  0 siblings, 1 reply; 8+ messages in thread
From: Thomas Jones @ 2005-08-24 18:14 UTC (permalink / raw)
  To: netfilter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I would like to formally request end-user submission of rulesets to the 
Security Document Initiative's Firewall Rule Subset ---- see the following 
resource for more information http://www.buddhalinux.com.

Abstract:
The Security Document Initiative is an implementation of the domain of applied 
cryptography as it relates to XML Markup Language and the creation of a 
security infrastructure to protect information systems and resources.

This project is charged with developing a XML Document Type Definition 
document model that Netfilter rulesets can be validated against. Any document 
instance of the "Firewall Rule Subset" must be well-formed and comply with 
the structured XML Markup Language. This language is being designed to 
provide all VALID rule entries that are available under the netfilter 
framework.

This is where you the end-user come into play. Obviously, it would take me an 
untold number of days/weeks/months/years to construct a comprehensive and 
stable compilation of valid rules. The compilation of the rules and rulesets 
are a key step in this development process. Without, all representative rules 
and rulesets; a correct and valid netfilter rule will be deemed invalid under 
an improperly constructed document model. Thus, negating the purpose and 
intent of the SDI Firewall Rule Subset project.

All submissions are held in complete confidentiality. You may choose to alter 
your rules and/or rulesets accordingly to obfuscate and mask the original 
address schemes. However, a confidentiality agreement will be made available 
to interested parties. Due care and diligence will be made to ensure end-user 
privacy. All submissions will be stored in encrypted form only on a 
non-networked medium.

Digitally signed and/or encrypted submissions are recommended.

I would like to thank the Netfilter community in advance for their 
contributions to this project.

Cheers,
Thomas Jones
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDDLkGoR5cE1e/kEIRAsc7AJ0ctaPsMyetjFpoR5efvRrdn3B2ogCffSmu
WCf1meG+lA4VS2NZHZSo7JE=
=u4s2
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2005-08-26 11:57 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-25 11:56 Request: Submission of Rulesets Derick Anderson
2005-08-25 14:35 ` Thomas Jones
  -- strict thread matches above, loose matches on Subject: below --
2005-08-26 11:57 Derick Anderson
2005-08-24 18:14 Thomas Jones
2005-08-24 21:07 ` /dev/rob0
2005-08-24 22:25   ` Thomas Jones
2005-08-24 22:36     ` /dev/rob0
2005-08-24 22:48       ` Thomas Jones

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.