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  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]
Date: Tue, 3 Feb 2004 12:55:24 -0800
From: Matthew Dharm <>
To: Patrick Proniewski <>
Cc: Thomas Zehetbauer <>,
	Liste BugTrack <>
Subject: Re: RFC: virus handling

On Wed, Jan 28, 2004 at 07:24:52PM +0100, Patrick Proniewski wrote:
> On 28 janv. 2004, at 16:45, Thomas Zehetbauer wrote:
> >Looking at the current outbreak of the Mydoom.A worm I would like to
> >share and discuss some thoughts:
> You bring some definitely interesting points here.
> I agree with your 1) and 2), but 3) rises some technical concern
> >3.1.2.) e-mail Alias and Web-Interface
> >Additionally providers should provide e-mail aliases for the IP
> >addresses of their customers (eg. customer at can be reached
> >via or a web interface with similiar
> >functionality. The latter should be provided when dynamically assigned
> >IP addresses are used for which an additional timestamp is required.
> could be a really good idea, if not so easy to use for spammers or even 
> for virii. The moment you setup such a service, spammers/virus coder 
> will write a script that can reach every single user with an active 
> connexion. It's a really major drawback I think.

Perhaps something with more limited functionality, then?

Consider a provider who offers the e-mail address of (name it what you will), to which can be fed an
e-mail consisting of a single line -- that line is the IP address and a
one-word 'name' for the problem. 

Thus, if I find I'm getting MyDoom.A from, I can send a message
that will alert _someone_ (who is presumeably not asleep at the controls).

It also means that general e-mail cannot be sent via this interface -- no
spamming.  The provider can take this information, look it up (with the
timestamp the e-mail came in at, if necessary for large dynamic pools), and
take action (the least of which, I hope, would be to notify the end-user).

This could even be done without e-mail at all.  A quick HTTP GET/POST could
carry this information.  Heck, this could run much like ident/auth
services to a designated machine (i.e.


Matthew Dharm                              Home: 
Senior Software Designer, Momentum Computer

					-- Greg
User Friendly, 11/28/97

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists