I'm not sure why there needs to be a separate file. I like having one file for all the common settings. I think the default should be backward compatible so that you can upgrade without causing problems.
I don't see why we need a separate keyword to turn allow on or off. As soon as declude sees an ALLOWEXT, all attachments that aren't specifically given an ALLOWEXT line would be blocked. All BANEXT lines after that would be ignored. If the first one declude sees is BANEXT, all attachments that aren't specifically given a BANEXT line would be allowed. All ALLOWEXT lines after that would be ignored. Either way would be fine with me, but I guess it really should be driven by what's possible, if either. Dan ---------- Original Message ---------------------------------- From: "John Tolmachoff" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Wed, 4 Dec 2002 08:49:29 -0800 >John S, I like your idea. > >Instead of having the current configuration in the virus.cfg of listing >banned extension, there could be one setting with multiple values like such: > >EXTENSIONS ALLOW This would only allow what is on the list >EXTENSIONS BLOCK This would only block what is on the list >EXTENSIONS NONE This would block all extensions >EXTENSIONS DEFAULT This would allow all extensions > >If EXTENSIONS was not defined, it would default. > >There would then be a separate file called extensions.txt where the list >would be kept. This would be the same file for either allow or block, and >you would list the appropriate ones. > >It seems like it would be easy enough to implement, but every time I think >that, I am proven wrong. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
