"Scott C. Best" wrote:
> ...
>
> Yikes, from schema to UI in 5 emails. :)
> Getting back (briefly) to the subject which spawned this thread,
> let me offer a collection of opinions:
>
> 1. To make UI design easier for everyone, it'd be *nice* if the user's
> intentions for the firewall were stored on the firewall in XML format.
> A firewall.conf, as it were.
>
> 2. Given this firewall.conf file, a middleware process/app/script would
> be needed to turn this data into the OS-specific firewall commands
> (e.g. ipchains, ipfwadm, netfilter, etc). This middleware piece could
> produce either a root-executable script, install the rules directly,
> or even do both.
>
> 3. Given #2, you don't care *how* #1 gets updated. It could be thru a
> command-line console interface, a LAN-based Windoze app, or a remote
> server running some ASP scripts connected via an SSH session. Or
> just vi.
>
> Is this a sensible design-model paradigm for LEAF?
Yep! You got my vote on #1. Once we have #1, it will then
drive/promote #2 & #3 naturally, and let the open source spirit takes
its course.
Cheers,
Ly
-----------
>
> -Scott
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-devel
--
"If you find yourself digging a deeper and deeper hole... stop digging."
- Anonymous
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
