- Re: Using fips.sys
- Posted by on June 30th, 2004
Such a document doesn't seem to be in the public domain, however the info in
http://www.microsoft.com/technet/sec...p.mspx?pf=true
is enough to figure out most of the rest.
"Geoff Kneller" <Geoff Kneller@discussions.microsoft.com> wrote in message
news:197C60B2-FC6D-4A83-B5D3-2BED2C2CC541@microsoft.com...
- Posted by Geoff Kneller on June 30th, 2004
Thanks for responding, yes I've read the security policy document but it contains this cryptic jewel:
Acquiring a Table of Pointers to FipsXXX Functions
A kernel mode user of the FIPS.SYS driver must be able to reference the FipsXXX functions before using them. The user needs to acquire the table of pointers to the FipsXXX functions from the FIPS.SYS driver. The user accomplishes the table acquisition by building a Fips function table request irp (I/O request packet) and then sending the irp to the FIPS.SYS diver via the IoCallDriver function. Further information on irp and IoCallDriver can be found on Microsoft Windows 2000 Driver Development Kit.
What is the IRP number to send to do this? What other IRP's does it understand?
"nospam@cristalink.com" wrote:
- Posted by on June 30th, 2004
Well, you can figure this out, say, by using a debugger. You have the
function names and prototypes, you only need the IRP params and a few more
bits. It's not that hard. Sorry, I cannot give away the info, though I can
provide a consultancy service.
"Geoff Kneller" <Geoff Kneller@discussions.microsoft.com> wrote in message
news:1A2A275E-807A-4CB9-8B49-E618EC692624@microsoft.com...
