One minor detail. The "depmod" and "modprobe" steps seem only to work when the "cryptoapi" directory is
placed under "/lib/modules/<kernel-version>/kernel", at least for 2.4.17 and the like.
Also, the "modprobe" step (or "insmod", if the modules are installed manually) complains loudly that the
module will "taint" the kernel because it has "no license":
root:/# modprobe cryptoloop
Warning: loading /lib/modules/2.4.17-686/kernel/cryptoapi/cryptoloop.o will taint the kernel: no license
What is this about?
All ciphers (except des, which is deprecated anyway) appear to be working! :-)
Thanks for the extra security!
Cheers. -- Harmon
Herbert Valerio Riedel wrote:
On Thu, 2001-12-27 at 00:30, Harmon S. Nine wrote:
Hi all.
I'm having a problem trying to build cryptoapi-2.4.7.0 for the 2.4.17 kernel. It has something to do with the EXPORT_SYMBOL macro. I'm using the Debian distribution on a 686 system. Thought I'd see if anyone knows a quick fix before I go digging ...
Here's the output from the "make" command in the cryptoapi-2.4.7.0 directory:
quick fix:
change the gcc line at the beginning of Makefile.common.in to contain -DEXPORT_SYMTAB ...
# $Id: Makefile.common.in,v 1.4 2001/10/19 17:52:59 hvr Exp $
# dynamic modules $(KMODULES): %.o: %.c $(KCC) -I$(top_srcdir)/include -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB $(KCPPFLAGS) $(KCFLAGS) -o $@ -c $<
regards,
- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
