[asterisk-dev] dahdi: module signature verification on fedora
sean darcy
seandarcy2 at gmail.com
Sun Jun 4 15:10:01 CDT 2017
installing newly built dahdi kernel modules, I get:
INSTALL
/home/asterisk/rpmbuild/BUILD/dahdi-linux-changes-for-4.11/drivers/dahdi/../staging/echo/echo.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:182
sign-file: certs/signing_key.pem: No such file or directory
.........
for all the modules.
googling taught me that Fedora has turned on "Module Signature
Verification", which seems to require a signing certificate. It seems
ubuntu also has it.
dahdi is the only time I build and install kernel modules. AFAICT, the
modules were installed, and did load.
Anybody else seeing this? How do you handle without getting your own pem
certificate ?
sean
More information about the asterisk-dev
mailing list