BugTraq
RFC: virus handling Jan 28 2004 03:45PM
Thomas Zehetbauer (thomasz hostmaster org) (13 replies)
Re: RFC: virus handling Jan 29 2004 08:39PM
Pavel Levshin (flicker mariinsky ru) (1 replies)
Hello, Thomas!
You wrote to <bugtraq (at) securityfocus (dot) com [email concealed]> on Wed, 28 Jan 2004 16:45:39 +0100:

TZ> 1.1.) Configuration
TZ> Unless the virus scanner provides special handling for worms and virii
TZ> which knowingly use a faked sender address it should not send out
TZ> notification messages unless the administrator has been warned that
TZ> these notification messages may not reach the intended recipient and
TZ> has still enabled this feature.

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 know many administrators who do not care of a few thousands antivirus
reports per day. No "warnings" are accepted. I would like to have some RFC
which disallows such behaviour, so I could send them all to RFC-ignorant BL.

TZ> 1.2.1.) Standardization
TZ> To allow filtering of these messages they should always carry the text
TZ> 'possible virus found' in the subject optionally extended by the name
TZ> of the virus or the test conducted (eg. heuristics).

It is unfair in relation to other languages. Many users do not read in
English, and Subject is supposed to be human-readable field. This
information could have standard form in other header.

TZ> 3.1.2.) e-mail Alias and Web-Interface
TZ> Additionally providers should provide e-mail aliases for the IP
TZ> addresses of their customers (eg. customer at 127.0.0.1 can be reached
TZ> via 127.0.0.1 (at) provider (dot) com [email concealed]) or a web interface with similiar
TZ> functionality. The latter should be provided when dynamically assigned
TZ> IP addresses are used for which an additional timestamp is required.

It tends to be non-standard interface, which is very hard to find and use.

With best regards, Pavel Levshin. E-mail: flicker (at) mariinsky (dot) ru [email concealed]

[ reply ]
Re: RFC: virus handling Feb 03 2004 01:26AM
David F. Skoll (dfs roaringpenguin com)
Re: RFC: virus handling Jan 29 2004 12:18PM
Sascha Wilde (wilde agentur-sec de)
RFC: content-filter and AV notifications (Was: Re: RFC: virus handling) Jan 29 2004 12:00PM
Andrey G. Sergeev (AKA Andris) (andris aernet ru) (1 replies)
Re: RFC: content-filter and AV notifications (Was: Re: RFC: virus handling) Feb 03 2004 04:07PM
Peter J. Holzer (hjp wsr ac at)
Re: RFC: virus handling Jan 28 2004 11:11PM
Pavel Kankovsky (peak argo troja mff cuni cz)
Re: RFC: virus handling Jan 28 2004 10:00PM
John Fitzgibbon (fitz jfitz com) (1 replies)
Re: RFC: virus handling Feb 03 2004 05:09PM
Dave Clendenan (dave dave clendenan ca) (1 replies)
Re: RFC: virus handling Feb 03 2004 10:59PM
Volker Kuhlmann (list0570 paradise net nz)
Re: RFC: virus handling Jan 28 2004 09:26PM
Craig Morrison (craig fishpalace org) (1 replies)
Re: RFC: virus handling Feb 03 2004 11:11AM
James C. Slora Jr. (Jim Slora phra com)
Re: virus handling Jan 28 2004 08:33PM
Mike Healan (mike spywareinfo com)
Re: RFC: virus handling Jan 28 2004 08:06PM
Dave Aronson (spamtrap secfocus dja mailme org)
Re: RFC: virus handling Jan 28 2004 07:08PM
Daniele Orlandi (daniele orlandi com)
Re: RFC: virus handling Jan 28 2004 06:48PM
Piotr KUCHARSKI (chopin sgh waw pl)
Re: RFC: virus handling Jan 28 2004 06:24PM
Patrick Proniewski (patpro patpro net) (1 replies)
Re: RFC: virus handling Feb 03 2004 08:55PM
Matthew Dharm (mdharm one-eyed-alien net) (1 replies)
Re: RFC: virus handling Feb 04 2004 01:44PM
Ben Wheeler (b wheeler ulcc ac uk) (1 replies)
Re: RFC: virus handling Feb 05 2004 12:52PM
Shawn McMahon (smcmahon eiv com)
Re: RFC: virus handling Jan 28 2004 06:07PM
Jeremy Mates (jmates sial org) (1 replies)
Hysterical first technical alert from US-CERT Feb 03 2004 12:11PM
Larry Seltzer (larry larryseltzer com) (3 replies)
Re: Hysterical first technical alert from US-CERT Feb 05 2004 12:18PM
Andreas Marx (amarx gega-it de)
Re: Hysterical first technical alert from US-CERT Feb 04 2004 02:31PM
Valdis Kletnieks vt edu (2 replies)
Re: Hysterical first technical alert from US-CERT Feb 05 2004 08:33AM
Stephen Samuel (samuel bcgreen com) (1 replies)
Re: Hysterical first technical alert from US-CERT Feb 06 2004 10:07PM
Valdis Kletnieks vt edu (1 replies)
Re: Hysterical first technical alert from US-CERT Feb 08 2004 01:01PM
Shawn McMahon (smcmahon eiv com)
RE: Hysterical first technical alert from US-CERT Feb 04 2004 02:41PM
Larry Seltzer (larry larryseltzer com) (1 replies)
Re: Hysterical first technical alert from US-CERT Feb 04 2004 05:11PM
Valdis Kletnieks vt edu
Re: Hysterical first technical alert from US-CERT Feb 04 2004 12:27PM
Philip Rowlands (phr doc ic ac uk)
Re: RFC: virus handling Jan 28 2004 05:54PM
3APA3A (3APA3A SECURITY NNOV RU) (1 replies)
getting rid of outbreaks and spam (junk) [WAS: Re: RFC: virus handling] Feb 03 2004 09:11AM
Gadi Evron (ge linuxbox org) (4 replies)
Re: getting rid of outbreaks and spam (junk) Feb 04 2004 08:07PM
James Riden (j riden massey ac nz)
Re: getting rid of outbreaks and spam (junk) [WAS: Re: RFC: virus handling] Feb 04 2004 08:04PM
Georg Schwarz (geos epost de)
Re: getting rid of outbreaks and spam (junk) [WAS: Re: RFC: virus handling] Feb 04 2004 06:27AM
der Mouse (mouse Rodents Montreal QC CA)
Re: getting rid of outbreaks and spam (junk) [WAS: Re: RFC: virus handling] Feb 03 2004 11:07PM
James A. Thornton (jamest u-238 infinite1der org)


 

Privacy Statement
Copyright 2010, SecurityFocus