Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 271993 Details for
Bug 365825
sys-apps/chpax: old style EI_PAX markings are deprecated and should be removed
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Remove chpax from pax-utils eclass
pax-utils.eclass (text/plain), 5.64 KB, created by
Anthony Basile
on 2011-05-03 17:20:47 UTC
(
hide
)
Description:
Remove chpax from pax-utils eclass
Filename:
MIME Type:
Creator:
Anthony Basile
Created:
2011-05-03 17:20:47 UTC
Size:
5.64 KB
patch
obsolete
># Copyright 1999-2011 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header: /var/cvsroot/gentoo-x86/eclass/pax-utils.eclass,v 1.10 2010/03/09 10:35:33 nyhm Exp $ > ># @ECLASS: pax-utils.eclass ># @MAINTAINER: ># Maintained by ># The Gentoo Linux Hardened Team <hardened@gentoo.org> ># Original Author ># Kevin F. Quinn <kevquinn@gentoo.org> ># Modifications for bug #365825, @ ECLASS markup ># Anthony G. Basile <blueness@gentoo.org> ># @BLURB: functions to provide pax markings ># @DESCRIPTION: ># This eclass provides support for manipulating PaX markings on ELF binaries, ># wrapping the use of the paxctl and scanelf utilities. It decides which to ># use depending on what is installed on the build host, preferring paxctl to ># scanelf. If paxctl is not installed, we fall back to scanelf since it is ># always present. However, currently scanelf doesn't do all that paxctl can. ># ># To control what markings are made, set PAX_MARKINGS in /etc/make.conf to ># contain either "PT" or "none". If PAX_MARKINGS is set to "PT", and the ># necessary utility is installed, the PT_PAX_FLAGS markings will be made. If ># PAX_MARKINGS is set to "none", no markings will be made. > >inherit eutils > ># Default to PT markings. >PAX_MARKINGS=${PAX_MARKINGS:="PT"} > ># @FUNCTION: pax-mark ># @USAGE: <flags> {<ELF files>} ># @RETURN: Shell true if we succeed, shell false otherwise ># @DESCRIPTION: ># Marks <ELF files> with provided PaX <flags> ># ># Flags are passed directly to the utilities unchanged. Possible flags at the ># time of writing, taken from /sbin/paxctl, are: ># ># p: disable PAGEEXEC P: enable PAGEEXEC ># e: disable EMUTRMAP E: enable EMUTRMAP ># m: disable MPROTECT M: enable MPROTECT ># r: disable RANDMMAP R: enable RANDMMAP ># s: disable SEGMEXEC S: enable SEGMEXEC ># ># Default flags are 'PeMRS', which are the most restrictive settings. Refer ># to http://pax.grsecurity.net/ for details on what these flags are all about. ># Do not use the obsolete flag 'x'/'X' which has been deprecated. ># ># Please confirm any relaxation of restrictions with the Gentoo Hardened team. ># Either ask on the gentoo-hardened mailing list, or CC/assign hardened@g.o on ># the bug report. >pax-mark() { > local f flags fail=0 failures="" zero_load_alignment > # Ignore '-' characters - in particular so that it doesn't matter if > # the caller prefixes with - > flags=${1//-} > shift > # Try paxctl, then scanelf. paxctl is preferred. > if type -p paxctl > /dev/null && hasq PT ${PAX_MARKINGS}; then > # Try paxctl, the upstream supported tool. > elog "PT PaX marking -${flags}" > _pax_list_files elog "$@" > for f in "$@"; do > # First, try modifying the existing PAX_FLAGS header > paxctl -q${flags} "${f}" && continue > # Second, try stealing the (unused under PaX) PT_GNU_STACK header > paxctl -qc${flags} "${f}" && continue > # Third, try pulling the base down a page, to create space and > # insert a PT_GNU_STACK header (works on ET_EXEC) > paxctl -qC${flags} "${f}" && continue > # Fourth - check if it loads to 0 (probably an ET_DYN) and if so, > # try rebasing with prelink first to give paxctl some space to > # grow downwards into. > if type -p objdump > /dev/null && type -p prelink > /dev/null; then > zero_load_alignment=$(objdump -p "${f}" | \ > grep -E '^[[:space:]]*LOAD[[:space:]]*off[[:space:]]*0x0+[[:space:]]' | \ > sed -e 's/.*align\(.*\)/\1/') > if [[ ${zero_load_alignment} != "" ]]; then > prelink -r $(( 2*(${zero_load_alignment}) )) && > paxctl -qC${flags} "${f}" && continue > fi > fi > fail=1 > failures="${failures} ${f}" > done > elif type -p scanelf > /dev/null && [[ ${PAX_MARKINGS} != "none" ]]; then > # Try scanelf, the Gentoo swiss-army knife ELF utility > # Currently this sets PT if it can, no option to control what it does. > elog "Fallback PaX marking -${flags}" > _pax_list_files elog "$@" > scanelf -Xxz ${flags} "$@" > elif [[ ${PAX_MARKINGS} != "none" ]]; then > # Out of options! > failures="$*" > fail=1 > fi > if [[ ${fail} == 1 ]]; then > ewarn "Failed to set PaX markings -${flags} for:" > _pax_list_files ewarn ${failures} > ewarn "Executables may be killed by PaX kernels." > fi > return ${fail} >} > ># @FUNCTION: list-paxables ># @USAGE: {<files>} ># @RETURN: Subset of {<files>} which are ELF executables or shared objects ># @DESCRIPTION: ># Print to stdout all of the <files> that are suitable to have PaX flag ># markings, i.e., filter out the ELF executables or shared objects from a list ># of files. This is useful for passing wild-card lists to pax-mark, although ># in general it is preferable for ebuilds to list precisely which ELFS are to ># be marked. Often not all the ELF installed by a package need remarking. ># @EXAMPLE: ># pax-mark -m $(list-paxables ${S}/{,usr/}bin/*) >list-paxables() { > file "$@" 2> /dev/null | grep -E 'ELF.*(executable|shared object)' | sed -e 's/: .*$//' >} > ># @FUNCTION: host-is-pax ># @RETURN: Shell true if the build process is PaX enabled, shell false otherwise ># @DESCRIPTION: ># This is intended for use where the build process must be modified conditionally ># depending on whether the host is PaX enabled or not. It is not intedened to ># determine whether the final binaries need PaX markings. Note: if procfs is ># not mounted on /proc, this returns shell false (e.g. Gentoo/FBSD). >host-is-pax() { > grep -qs ^PaX: /proc/self/status >} > > ># INTERNAL FUNCTIONS ># ------------------ ># ># These functions are for use internally by the eclass - do not use ># them elsewhere as they are not supported (i.e. they may be removed ># or their function may change arbitratily). > ># Display a list of things, one per line, indented a bit, using the ># display command in $1. >_pax_list_files() { > local f cmd > cmd=$1 > shift > for f in "$@"; do > ${cmd} " ${f}" > done >} >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 365825
: 271993