[EMAIL PROTECTED] wrote: > He should make himself a website and post his work on it, then send > clients links to the website. Oh, and he should sign his work with a > certificate and give the clients his public key so they can confirm > he was the one who wrote it.
Dennis Peterson wrote:
If you have user space locked down adequately and are sure you won't be sued for facilitating the transfer of hazardous files (unless you know they are not, best to assume they are), allow the users to build a dropbox. Require scp or sftp, for upload, and then password protect the data file in case the link to it gets loose in the wild. Require .htaccess or other authentication. Sweep the file area to remove files after an agreed upon time frame.
Which was one option I was already considering, and is exactly what we have now done. The customer in question jumped at the chance to get (.htaccess protected) web space anyway. In a way, I was expecting more resistance from that particular guy, but that's a long story.
Now all our Amavis/ClamAV settings are back to their most restrictive again. Lord knows, that's certainly how I would prefer it.
Thanks once again for everyone's input. I truly appreciate it!
-- Jason Byrns System Administrator, MicroLnk http://www.MicroLnk.com/ 402-328-8600 ext. 653 _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
