Hi,

I've got a quick question about using openssl within custom kernel modules that are loaded at runtime.

1) Is openssl designed to be used within kernel modules?
   Specifically I want to use some the des and aes encryption routines.

I have a kernel module (for an embedded system) that includes <openssl/des.h> from 0.9.6d. It compiles and runs :) I have upgraded to 0.9.8 and I now get *lots* of warnings and errors because many CPP macros are being redefined, etc. I figured that any kernel code (including external modules) should not use outside libraries such as glibc, openssl, etc.
2) Is that a correct interpretation?

3) If I am wrong and it is allowed to use openssl in kernel modules, then how does one stop system header files interfering with kernel/linux header files ??? eg. <sys/*> files, etc.

Cheers,
Brendan Simon.
(Please CC me as well as the list)

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to