full-disclosure - Has m$ fixed the fun with SetWindowsHookEx?

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

Message-ID: <200310171522.SAA06818@home.ntrl.net>
From: guninski at guninski.com (Georgi Guninski)
Subject: Has m$ fixed the fun with SetWindowsHookEx?

Has m$ fixed the fun with SetWindowsHookEx?

Description and example is here:
http://groups.google.com/groups?selm=10166542142.20020807095713%40sandy.ru&oe=UTF-8&output=gplain

IIRC it used to work once upon a time.
According to the lame m$ advisory on win2k it is possible to open windows with system privileges.

georgi