full-disclosure - Can DCOM be disabled safely?

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 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]

From: pauls at utdallas.edu (Paul Schmehl)
Subject: Can DCOM be disabled safely?

--On Saturday, August 02, 2003 10:05:00 +0100 CHeeKY 
<cheekypeople@...33.com> wrote:

> As previously discussed with you Paul, I am sorry but your policy of how
> you update and what you do seems somewhat backward, havent you ever heard
> of third party software

Of course I have.  And as I stated in a previous post, if I had a million 
dollars I'd *buy* all that third party software.  But I don't, so I can't.

> or even weirder, making your own.
>
Oh yeah.  I have time for that.  I *have* written several things to 
automate certain processes as have many others in IR at UTD (as do many 
edus, for the same reasons, no money to buy commercial solutions), but 
there are only so many hours in a day.

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu