full-disclosure - bypassing Windows Domain Group Policy Objects

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

Message-ID: <005a01c66a08$cb5202f0$1214dd80@corp.emc.com>
Date: Thu Apr 27 15:42:30 2006
From: exibar at thelair.com (Exibar)
Subject: bypassing Windows Domain Group Policy Objects


----- Original Message ----- 
From: "Michael Holstein" <michael.holstein@...ohio.edu>
To: <full-disclosure@...ts.grok.org.uk>
Sent: Thursday, April 27, 2006 10:37 AM
Subject: Re: [Full-disclosure] bypassing Windows Domain Group Policy Objects


>> System Key: 
>> [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System]
>> Value Name: DisableGPO
>> Data Type: REG_DWORD (DWORD Value)
>> Value Data: (0 = default, 1 = disable group policy)
>
> strike that .. production releases ignore this.
>
> Other possible solution, cripple gpupdate.exe (XP) or secedit.exe (2K) 
> through permissions (eg: remove 'localsystem:execute'). Deleting them will 
> just trigger WFP to replace.
>
> /mike.
>


   Hmmmm.....  sounds like a good plan :-)   I'll test that out!   thanks!

  Ex