lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 18 May 2007 22:27:06 +0200 (MEST)
From:	Jan Engelhardt <>
To:	John Sigler <>
Subject: Re: Dumping the checksums in a module

On May 18 2007 17:02, John Sigler wrote:
> I'm getting "disagrees about version of symbol struct_module" messages,
> and I'm trying to understand why.
> As far as I understand (which is not very far), if I define
> CONFIG_MODVERSIONS, then checksums for various functions (all exported
> functions?) and various structures (which ones?) will be included inside
> the kernel image, and written to Module.symvers. When an out-of-tree
> module is built, it will also include these checksums.
> How do I list the checksums within a module?
> Is there a simpler way to list all the checksums?

22:25 ichi:~ > modinfo aes
srcversion:     8CB82B3A254D5A950FD0D14

I think this one checksum is computed out of all functions that
the module uses.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists