full-disclosure - Question for the Windows pros

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: <162D1A70B0A84D5873AECDF1@utd59514.utdallas.edu>
Date: Thu Jan 19 16:28:59 2006
From: pauls at utdallas.edu (Paul Schmehl)
Subject: Question for the Windows pros

--On Thursday, January 19, 2006 10:32:44 +0100 Nicolas RUFF 
<nicolas.ruff@...il.com> wrote:
>
> The ImpersonateNamedPipeClient() risks have been fully documented by
> Blake Watts back in 2002.
> http://www.blakewatts.com/namedpipepaper.html
>
Does the Impersonate a client after authentication privilege grant the 
account access to ImpersonateNamedPipeClient?

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