Egads as this one spiraled up. :) Quick thoughts:
> > I agree. And while I do not mind the command line, it is often nice to
> > have a well crafted tool or interface help you and also reduce the chance
> > of errors.
>
> Absolutely - but non-commandline doesn's necessarily mean some x-interface.
> Granted, to the average windows user, anything less than 1024x768 with 16k
> colors _seems_ like a command line ;-) (no offense to anybody - I'm a
> "windows user" as well).
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?
-Scott
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
