[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-Disclosure] Why does a home computer user need DCOM?
- To: full-disclosure@xxxxxxxxxxxxxxxx
- Subject: Re: [Full-Disclosure] Why does a home computer user need DCOM?
- From: hobbit@xxxxxxxxx (*Hobbit*)
- Date: Wed, 10 Sep 2003 13:31:34 +0000 (GMT)
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*
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html