In theory, this should work...but it doesn't.
#! perl -slw
use strict;
use Encode;
use Devel::Peek;
use Win32::API::Prototype;
ApiLink( 'advapi32', q[
DWORD QueryUsersOnEncryptedFile(
LPCWSTR lpFileName,
ULONG pUsers
)
]) or die $^E;
my $buffer = chr(0) x 4;
print Dump( $buffer );
my $pointer = unpack 'L!', pack 'P', $buffer;
printf "%08x\n", $pointer;
my $uFile = encode( 'UTF-16LE', $_ = $ARGV[ 0 ], 1 );
print $uFile;
QueryUsersOnEncryptedFile(
$uFile,
$pointer
) or die "$! : $^E";
print Dump( \$buffer );
print unpack 'C*',$buffer;
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|