From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Porting PaX to the ia64
Date: 31 Aug 2003 10:58:55 -0400 [thread overview]
Message-ID: <1062341934.4083.7860.camel@simple> (raw)
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
Quote from the PaX docs.
----------------------------------------------------------------------
The goal of the PaX project is to research various defense mechanisms
against the exploitation of software bugs that give an attacker
arbitrary read/write access to the attacked task's address space. This
class of bugs contains among others various forms of buffer overflow
bugs (be they stack or heap based), user supplied format string bugs,
etc.
----------------------------------------------------------------------
If you have an ia64 and your bold, brave and want to be on the bleeding
edge of security solutions then your in luck. The PaX Team has come up
with with an experimental patch for the ia64 that needs some testing
from a few somebody's that own or have root access to ia64
Grab yourself these three files to begin testing.
* ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2.4.22.tar.bz2
* http://pageexec.virtualave.net/pax-linux-2.4.22-200308271615.patch
* http://grsecurity.net/~paxguy1/pax-linux-2.4.22.patch.ia64
unpack the kernel
add the pax-linux-2.4.22-200308271615.patch
add the pax-linux-2.4.22.patch.ia64
Enable pax in your kernel with as many options as your willing to help
test.
Compile the kernel
# make menuconfig
# make dep bzImage modules modules_install
tell your bootloader to use the arch/ia64/bzImage file
reboot and report success/failures via email to pageexec@freemail.hu and
or real-time on irc.freenode.net in #pax
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux Developer (Hardened)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
reply other threads:[~2003-08-31 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1062341934.4083.7860.camel@simple \
--to=solar@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox