full-disclosure - Why does a home computer user need DCOM?

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

Message-ID: <20030910133134.4A688C309@relayer.avian.org>
From: hobbit at avian.org (*Hobbit*)
Subject: Why does a home computer user need DCOM?

Once again, I wouldn't mind a way to turn off *ALL* the RPC stuff,
including the RPC service itself, without paying the price of having
almost everything I do afterward just sit there and stupidly wait for it
to respond.  A box with it disabled *will* run, just barely, it'll just
be sluggish as hell.

Or at the very least a way to run it so it doesn't listen on a socket
bound to *.  How 'bout localhost-only, or the equivalent of unix-domain
pipes, or *something* to keep it insulated from the network??  How 'bout
the same for SMB/tcp 445?

Argh.  There's probably some registry hack that *could* do that.

_H*