I've been doing lots of research into this very problem lately, and unfortunately I don't have a solution for you at this time.
It's not as easy as simple changes in the pwdump2 code. I'm pretty familiar with this source code, so read on for some technical details... the code needs to open the lsass.exe process, for which it needs SeDebugPrivilege privilege. However, under a normal user account, this privilege is not even in the process token. This means that you can't enable it. Todd Sabin's pwdump2 source doesn't correctly error check the AdjustProcessToken call that it makes, so you don't realize the reason it fails w/o admin access. And it's not as simple as ENABLING the SeDebug privilege, because the token doesn't contain that priv to begin with.
If I'm confusing anyone, here's a summary. The methodology that pwdump2 uses requires a special privilege that can be had only by an administrative account. I haven't found a simple way around that yet, but still doing a lot of research.
You might want to check out an NT rootkit. _http://www.rootkit.com. Possible answer to your problem here, but it's not going to be a simple point-click installation.


LinkBack URL
About LinkBacks


Reply With Quote
