From: Mij <mi...@ss...> - 2010-07-04 23:34:11
|
I've been considering this. There are some thought holding it back, like - one parser is already incumbent in the code, combining two parsers is some pain - parsing has a terrible code/functionality ratio, it's a pity to deploy it for something as ancillary as configuration files - having configuration files would finally mark sshguard a "serious" daemon :) rather than a tool I've found the "envdir" configuration style (that's "configuration directory"es rather than files) tremendously lean and convenient from both the user and the programmer; how would that fit in your daemon script frame? On Jun 1, 2010, at 06:57 , Julián Moreno Patiño wrote: > Hi Mij, > > It would be nice to implement a configuration file sshguard.conf to enable options such as log sucker, whitelisting, blacklisting, port service and use them in different services (sshd, sendmail, exim, dovecot, etc), it's more easier and I can create more generic daemon script to Debian Distribution. > > Thank you very much, see you. > > Kind Regards, > > -- > Julián Moreno Patiño > Registered GNU Linux User ID 488513 > PGP KEY ID 6168BF60 > ------------------------------------------------------------------------------ > > _______________________________________________ > Sshguard-users mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/sshguard-users |