Jose-Marcio Martins da Cruz wrote: > Hello, > > I have two suggestions : > > * It could be interesting to add tcp_wrapper (or equivalent - not so > difficult to code it) support to clamd. >
This sounds good. tcp-wrappers would add security to clamds listening to a network which seems to be lacking. > * When running configure, it could be interesting to display a summary > when it finishes : what libraries wasn't found, what's lacking, a > summary of what was selected, what can't be build (as some conditions > weren't met, ... Usually people don't look at all configure rants... so > the summary may be useful. > I don't think it is a good idea to add extra summary code to ./configure. I don't like it when other programs do this because it departs from the normal output of ./configure scripts. Maybe if a configure option --enable-all or --with-all was added, the configure script could die immediately after a test fails and a certain part of clamav is disabled. Then the user could add --disable-feature or --without-package until all tests passed - then he'd know exactly what his clamav can/can't do. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
