[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c676d304-85af-6878-ca5c-75530e91a57a@riseup.net>
Date: Mon, 18 Nov 2019 19:09:00 +0000
From: Patrick Schleizer <adrelanos@...eup.net>
To: lkrg-users@...ts.openwall.com
Subject: LKRG compilation hardening flags
Could you please kindly have a look and let me know if something needs
fixing?
(This is what happened building LKRG using DKMS. Shouldn't make a
difference though, since it is using the usual upstream makefile.)
checksec -f /lib/modules/4.19.0-6-amd64/updates/dkms/p_lkrg.ko
RELRO STACK CANARY NX PIE RPATH
RUNPATH Symbols FORTIFY Fortified Fortifiable FILE
No RELRO Canary found NX disabled Not an ELF file No
RPATH No RUNPATH 866 Symbols Yes 0 2
/lib/modules/4.19.0-6-amd64/updates/dkms/p_lkrg.ko
hardening-check /lib/modules/4.19.0-6-amd64/updates/dkms/p_lkrg.ko
/lib/modules/4.19.0-6-amd64/updates/dkms/p_lkrg.ko:
Position Independent Executable: not a known ELF type!? ()
Stack protected: yes
Fortify Source functions: no, only unprotected functions found!
Read-only relocations: no, non-ELF (ignored)
Immediate binding: no, non-ELF (ignored)
I guess, should something need fixing, it's a task for the upstream
makefile?
Kind regards,
Patrick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
