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

Message-ID: <1405A2886E3F0744B9A567C7B90F7664374154@EVS-1.b-online.com.au>
Date: Fri Apr 28 01:51:27 2006
From: Neil.Hunt at bdigital.com.au (Neil Hunt)
Subject: bypassing Windows Domain Group Policy Objects

Michael Holstein said:
> >
> > 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.
> >
Exibar said:
> 
> 
>    Hmmmm.....  sounds like a good plan :-)   I'll test that 
> out!   thanks!
> 
>   Ex 
> 

This does indeed work, but, if the site is using WSUS or similar, then
the machine will stick out like a sore thumb.  The windows admin here,
however, doesn't monitor WSUS, so that fact that my machine hasn't
reported in 90 days hasn't registered.

Neil