Re: [TuxFrw-devel] TuxFrw 2.16-pre1...

[Marcelo de S. <ma...@ac...>]

Hello Jean! (excuse me to call you so...)

Your idea is great! You're certainly on the right track, going toward the same
point as we are. Undoubtedly Perl brings the power that we need to make our
scripts, and as we can see you manage the Perl language very well.

As you can see our intention is to create some sort of assistants that can
help creating the "tuxfrw.conf" files (and things like that). We should focus
on the development of that sort of scripts, not forgetting the base TF rules,
of course. This way, with a powerful configuration script we can "fine tune"
our "generic" set of rules into a customized one.

Your contribution lead me to understand that you are really interested on the
"config" part of the software. This is great, and I think this could be a
"task" for you to take care of. To summarize, I'd really like to have your help
with this part of the work, as we'd be sending you the "final/base" tuxfrw.conf
file, and you could do the conf scripts to achieve that file.

Well... I know things are a little bit "dark" now, as we pass through a new
stage of development. This week I've been working heavily on TF to think about
a way to make users' life easier, and as you can see there it is (TF 2.16-pre1
functionality). So, as I promised, I'll soon send some sort of "road-map" to
be followed by those who wanna help...

That's all.

See you later...


Quoting Jean Jacques Gervais <jj...@in...>:

> Hi  all!
> 
> I have looked  at install.sh and tuxfrw-config.sh and I think I can see
> toward 
> what you are going.   I did some testing on my own, just to see what was 
> possible to do with perl.  
> 
> So I did a small perl script (test.pl) that is going in the same direction
> as 
> tuxfrw-config.sh.  My test is more like a configuration assistant than an 
> installation assistant. My objective is just to see towards what we are 
> heading  to and see what can be done with perl.
> 
> In this test, i have:
> 
> - reading tux configuration file to map tux variables to perl variables
> - dig kernel information: am i root ?, kernel version,  release version,
> host 
> name,  domain name ...
> - interface detection
> - a first menu structure
> - showing actual tux configuration and kernel information
> 
> I think it would be interresting that the installer and the assistant would
> 
> remember past answers from previous installation.   The assistant could read
> 
> the tuxfrw.conf script, read in the actual values and give the user the 
> opportunity to change the configuration.
> 
> The assistant could verify the installation and help in TF upgrade.  The 
> installer could help in detecting and preventing configuration problems (a
> 
> ppp interface choosen as an the internal interface, the same interface 
> choosen twice ...).
> 
> I my on the right track ?  What do we do now ?  Do you think it is wortwhile
> 
> to continue this test ?  
> 
> Jean Jacques Gervais
> 
> p.s. Can you guys from Brazil send us some sun, it's cold in Montréal.
> 
> - On Friday 24 May 2002 16:29, Marcelo de Souza wrote:
> > Hi all!
> >
> > I'd like to announce TF 2.16 pre release 1.
> >
> > There are lots of changes, specifically concerning TF structure. I
> haven't
> > made any changes to the iptables ruleset, only to the way TF is
> > installed/configured/organized...
> >
> > I prefer to send u my developing notes later. By now u should try to
> > understand what I've done...
> >
> > This way I want to automate TF process even more, asking the user about
> the
> > profile of the network and its services.
> >
> > Well, that's all. I'll soon be sending some of my notes and a roadmap
> for
> > the future...
> >
> > Bye!
> >

------------------------------------------------------------ 
   - MARCELO DE SOUZA -            <ma...@ac...> 
 
   Computer Science / UNESP - S. J. Rio Preto, SP, Brazil 
 
         -- ACME! Computer Security Research -- 
 
            http://www.acme-ids.org/~marcelo 
------------------------------------------------------------ 


-------------------------------------------------
       ACME! Computer Security Research
           http://www.acme-ids.org