I don't have any experience with Windows kernel space code, but looking at the following quote from http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx, it doesn't look very good:

Anything involving class hierarchies or templates, exceptions, or any form of dynamic typing is likely to be unsafe. Using these constructs requires extremely careful analysis of the generated object code. Limiting use of classes to POD classes significantly reduces the risks.

If you just need AES-GCM, you're probably better off using plain C code, instead of trying to pare down Crypto++ to something safe in kernel mode. Here's one: http://gladman.plushost.co.uk/oldsite/AES/index.php

Also, is it possible to do what you need in user mode? This link may or may not be useful: http://msdn.microsoft.com/en-us/library/ms892537.aspx

--------------------------------------------------
From: "jbeaujon" <[email protected]>
Sent: Thursday, January 14, 2010 1:36 PM
To: "Crypto++ Users" <[email protected]>
Subject: Using Crypto++ in NDIS 5.x/6.x driver ?

Hi,

Wondering if anybody has had success (or even tried) to use Crypto++
in a Windows NDIS driver...  After a brief look at the code, it seems
that porting to the kernel may prove to be difficult due to the use of
exceptions and inline assembler (for x64 at least).

Currently, all I need is AES GCM, so paring down the number of files
to just those necessary to do GCM might provide an easier path than
porting the entire library.  Is anyone successfully building a subset
of the library for either kernel or user space ?

Thanks in advance,

Jeff




--
You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.

-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.

Reply via email to