linux-kernel - Regarding PaX

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 6 Dec 2016 18:03:32 +0530
From:   manjunatha srinivasan <manjunathan.n@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Regarding PaX

Hi

I am new to PaX.

I have plan to port only PaX (i.e mutual exclusive write/execute
pages) for 4.1 kernel (kernel.org) for x86_64 architectures. From
other place I found patch from
(https://git.m-privacy.de/linux-mprivacy-4.1.git) from branch
'paxonly' for  4.1  kernel. From the commit ID
9474667100c85c944a0d71ede82ef85e3ab502dc (123248 lines)
I don't' know where to start from this commit. Please let me know
about information on internals i.e. about code implementation and
related documents of PaX ( i.e. mutual exclusive write/execute
pages.).

Also if want to do of porting PaX (i.e mutual exclusive write/execute
pages) from scratch where can I find internals of it. Is that
information from https://pax.grsecurity.net/ is enough idea for kick
start.
Please let me know the prerequisite knowledge on Linux subsystem like
memory management before starting.

If you feel this not the correct place of asking, please advice where
should I post.

Thanks & Regards
Manjunatha Srinivasan N