bugtraq - Re: RFC: virus handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.0402022024180.5507@shishi.roaringpenguin.com>
Date: Mon, 2 Feb 2004 20:26:38 -0500 (EST)
From: "David F. Skoll" <dfs@...ringpenguin.com>
To: Pavel Levshin <flicker@...iinsky.ru>
Cc: Thomas Zehetbauer <thomasz@...tmaster.org>,
	bugtraq@...urityfocus.com
Subject: Re: RFC: virus handling


On Thu, 29 Jan 2004, Pavel Levshin wrote:

> Antivirus software MAY be configured to send notifications to local senders
> and/or recipients, i.e. to domains which are handled by this server.
> Antivirus filtering software SHOULD NOT be configured to send out
> notifications to senders or recipients other than local, unless it
> distinguishes between faked and real addresses.

I would add:

"If anti-virus filtering software sends notifications to non-local
 recipients, then the sender address of the notifications MUST be an
 address that can be replied to, and this reply MUST reach a human
 being."

Rationale:  When my filtering software bounces all these stupid notifications,
I want a person to get stuck with all the bounce messages, thereby encouraging
him/her to turn off non-local notifications.

--
David.