full-disclosure - RE: Probable new MS DCOM RPC worm for Windo ws

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] [day] [month] [year] [list]

Message-ID: <Pine.NEB.4.58.0309261429190.18898@panix2.panix.com>
From: jays at panix.com (Jay Sulzberger)
Subject: RE: Probable new MS DCOM RPC worm for Windo
 ws


On Fri, 26 Sep 2003, Schmehl, Paul L wrote:

> > -----Original Message-----
> > From: Gary Flynn [mailto:flynngn@....edu]
> > Sent: Friday, September 26, 2003 8:06 AM
> > To: 'full-disclosure@...ts.netsys.com'
> > Subject: Re: [Full-Disclosure] RE: Probable new MS DCOM RPC
> > worm for Windo ws
> >
> >
> > I would think a better way of determining if a patch is
> > actually installed on a system is by examining the files on
> > the system rather than to depend upon symptoms (scanners) or
> > installation logs (registry entries).
>
> True, but *I'm* not going to physically touch (or even virtually touch)
> 2000+ machines looking at file properties.  Are you?
>
> Paul Schmehl (pauls@...allas.edu)

Why should not each and every machine report the status of its files?

oo--JS.