Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 50486 invoked from network); 16 Nov 2010 15:50:41 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Nov 2010 15:50:41 -0000 Received: (qmail 59543 invoked by uid 500); 16 Nov 2010 15:51:11 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 59518 invoked by uid 500); 16 Nov 2010 15:51:11 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 59509 invoked by uid 99); 16 Nov 2010 15:51:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Nov 2010 15:51:10 +0000 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ziggythehamster@gmail.com designates 209.85.161.172 as permitted sender) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Nov 2010 15:51:05 +0000 Received: by gxk27 with SMTP id 27so436074gxk.31 for ; Tue, 16 Nov 2010 07:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Kjyuj5hhzfPwcjLhO/bnpQQNP179wVCUmYrbD9KAlwQ=; b=mhw8Ac92p172Q3z3Oth8cFTmGTzAzdp2LrUtfYMfMnBk1rto7ixrhwzB0dMzsgi6PQ 0EU5VSNiK0LEHHnvp59oFN1uS/MaQPpieznPjb9zms56QWSFsFjItbaprJWGWhdmfGwr wXeztPuVRNBoOikTDoZK7v0NntI7OcwSFYtws= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=PJor5Fzmn014ip1epV9rGXFF6GVetHBVi2W4CFKDC9vrIR2aJM+v+ACwDW/Z7N+Z7U R2Q7nNOSNifiLvWe4PLaJfgIxzkEQHQWbnspxklPL4+Jacfo5+0LyePxXLGnDG9wcF2d 5S3Zi/UFwgF1QYzrhFqvcMp3SN5CckqdPSkvA= MIME-Version: 1.0 Received: by 10.91.17.20 with SMTP id u20mr9901479agi.96.1289922644727; Tue, 16 Nov 2010 07:50:44 -0800 (PST) Received: by 10.90.94.7 with HTTP; Tue, 16 Nov 2010 07:50:44 -0800 (PST) In-Reply-To: <12623878.1554641289908630584.JavaMail.defaultUser@defaultHost> References: <12623878.1554641289908630584.JavaMail.defaultUser@defaultHost> Date: Tue, 16 Nov 2010 09:50:44 -0600 Message-ID: Subject: Re: content / attachment scanning From: Keith Gable To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 16, 2010 at 5:57 AM, bacco77@libero.it wrote: > I was wondering whether Couch-Db has anything for visurs scanning while uploading attachments. > I don't know, something like a Symantec remote service,configurable, etc. And a quarantine to put those files checked positive. On CouchDB, you'd do this in your application before attaching the file. Ideally, you'd have CouchDB set up in such a way that a virus would not be able to do any damage if, for some reason, it executed. I personally use Grsecurity to accomplish this on my production servers (which aren't running CouchDB but should work with CouchDB). If you wanted to use CouchDB to host a virus database, then you'd want to store a property for if it was scanned and the result of the scan. Just having a file attached isn't going to "infect" a computer. You have to execute the program, and I'm not sure that CouchDB stores attachments in such a way that it would be possible to do that.