|
I've been meaning to bring this up for
awhile...
When tmda-cgi is compiled, it creates a tmda.cgi
program that has all of the settings compiled in via #define statements.
If you want to make a change to the settings, you have to reconfigure and
recompile from the source.
I have most of the setup for building it to a
RPM. In the past, I've only built one configuration (pop3 authentication),
but this is really pretty inflexible. What we really need is the ability
to configure it after installation.
Rather than having all the settings #defined in the
header file, we could instead write the configuration to a separate file.
This could be really simple, maybe in the format "VARIABLE=value". If it
was in this format, we could simply read it in and putenv the settings, which
gets it all in the same place it ends up now.
I do understand that the more code we add to
tmda-cgi.c, the more chance that we will add a security hole to the program, but
I think that we have to do a little something to increase the
flexibility.
In addition to changes to tmda-cgi.c, we would need
to change configure to have the ability to only generate the configuration file
- easy.
Thoughts?
|
_________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
