]> git.ipfire.org Git - thirdparty/kmod.git/commit
testsuite: port signature-check modules to module-playground
authorLucas De Marchi <lucas.demarchi@intel.com>
Sat, 21 Feb 2015 17:47:16 +0000 (15:47 -0200)
committerLucas De Marchi <lucas.demarchi@intel.com>
Sat, 21 Feb 2015 17:51:42 +0000 (15:51 -0200)
commit3f0eb43b6de450bcf5f722da6567c452e417399d
tree2c9efb1d19a66f5ac64492860bf1b74481dbcdb9
parent77fdc66429a85763fd3e2022462d1be758d903ec
testsuite: port signature-check modules to module-playground

We use a "fake signature" to sign the modules. As far as kmod is
concerned the signature fields are informational only. It's the kernel
the responsible for checking it's valid.

So what we are doing here is: pick the signatures of the ext4-x86_64.ko
module and save as dummy.{hashalgo}. This signature is appended to the
mod-simple.ko module so the ext4-x86_64.ko module can be removed from
tree.
testsuite/module-playground/dummy.sha1 [new file with mode: 0644]
testsuite/module-playground/dummy.sha256 [new file with mode: 0644]
testsuite/populate-modules.sh
testsuite/rootfs-pristine/test-modinfo/correct-sig_hashalgo.txt [new file with mode: 0644]
testsuite/rootfs-pristine/test-modinfo/correct-sig_key.txt [new file with mode: 0644]
testsuite/rootfs-pristine/test-modinfo/correct-signer.txt [new file with mode: 0644]
testsuite/rootfs-pristine/test-modinfo/ext4-x86_64-sha1.ko [deleted file]
testsuite/rootfs-pristine/test-modinfo/ext4-x86_64-sha256.ko [deleted file]
testsuite/test-modinfo.c