From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BECAD1381F3 for ; Sat, 10 Nov 2012 22:22:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7964B21C00D; Sat, 10 Nov 2012 22:22:15 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EA18A21C00D for ; Sat, 10 Nov 2012 22:22:14 +0000 (UTC) Received: from hornbill.gentoo.org (hornbill.gentoo.org [94.100.119.163]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id A3C2233D938 for ; Sat, 10 Nov 2012 22:22:13 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by hornbill.gentoo.org (Postfix) with ESMTP id F1FD0E5436 for ; Sat, 10 Nov 2012 22:22:11 +0000 (UTC) From: "Anthony G. Basile" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Anthony G. Basile" Message-ID: <1352586115.5d7037d9dc58e4c0a94ac4dfb30af7dca0e6a2c6.blueness@gentoo> Subject: [gentoo-commits] proj/elfix:master commit in: doc/ X-VCS-Repository: proj/elfix X-VCS-Files: doc/paxctl-ng.1 doc/paxctl-ng.pod X-VCS-Directories: doc/ X-VCS-Committer: blueness X-VCS-Committer-Name: Anthony G. Basile X-VCS-Revision: 5d7037d9dc58e4c0a94ac4dfb30af7dca0e6a2c6 X-VCS-Branch: master Date: Sat, 10 Nov 2012 22:22:11 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: 3e14e04d-b7b2-4db8-aac2-5340abec17b7 X-Archives-Hash: 13c85a59007f4392588871d062f89d4e commit: 5d7037d9dc58e4c0a94ac4dfb30af7dca0e6a2c6 Author: Anthony G. Basile gentoo org> AuthorDate: Sat Nov 10 22:21:55 2012 +0000 Commit: Anthony G. Basile gentoo org> CommitDate: Sat Nov 10 22:21:55 2012 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=proj/elfix.git;a=commit;h=5d7037d9 doc/paxctl-ng.{pod,1}: update documentation for -L -l flags --- doc/paxctl-ng.1 | 23 ++++++++++++++++------- doc/paxctl-ng.pod | 23 ++++++++++++++++------- 2 files changed, 32 insertions(+), 14 deletions(-) diff --git a/doc/paxctl-ng.1 b/doc/paxctl-ng.1 index 5a57a33..2f3a904 100644 --- a/doc/paxctl-ng.1 +++ b/doc/paxctl-ng.1 @@ -147,6 +147,10 @@ paxctl\-ng \- get or set the PaX flags for both PT_PAX and XT_PAX markings .PP \&\fBpaxctl-ng\fR \-f [\-v] \s-1ELF\s0 .PP +\&\fBpaxctl-ng\fR \-L [\-v] \s-1ELF\s0 +.PP +\&\fBpaxctl-ng\fR \-l [\-v] \s-1ELF\s0 +.PP \&\fBpaxctl-ng\fR [\-h] .SH "DESCRIPTION" .IX Header "DESCRIPTION" @@ -172,13 +176,14 @@ Extended Attributes, otherwise these are lost, unlike \s-1PT_PAX\s0 markings whi are carried within the binary itself. .PP \&\fBpaxctl-ng\fR is opportunistic without taking control away from the user. If both -a \s-1PT_PAX\s0 program header and \s-1XT_PAX\s0 extended attribute field \*(L"user.pax\*(R" exist, and -then both markings will be equally updated when the user modifies the flags. If -only one marking exists, then only that marking will be updated. Under no circumstances -will \fBpaxctl-ng\fR create a \s-1PT_PAX\s0 program header. It will attempt to create an \s-1XT_PAX\s0 -extended attribute field if it is instructed to do so with the \-C or \-c flag, -and it will attempt to synchronize the \s-1PT_PAX\s0 and \s-1XT_PAX\s0 markings if given the \-F -or \-f flag. +a \s-1PT_PAX\s0 program header and \s-1XT_PAX\s0 extended attribute field \*(L"user.pax\*(R" exist, then +both markings will be equally updated when the user modifies the flags, unless the +\&\fB\-L\fR or \fB\-l\fR flags are given, limiting the markigs to just \s-1PT_PAX\s0 or \s-1XT_PAX\s0. If +only one marking is possible, then only that marking will be updated. Under no +circumstances will \fBpaxctl-ng\fR create a \s-1PT_PAX\s0 program header as \fBpaxctl\fR does. +It will only attempt to create an \s-1XT_PAX\s0 extended attribute field if it is instructed +to do so with the \-C or \-c flag, and it will attempt to synchronize the \s-1PT_PAX\s0 and +\&\s-1XT_PAX\s0 markings if given the \fB\-F\fR or \fB\-f\fR flag. .SH "OPTIONS" .IX Header "OPTIONS" .IP "\fB\-P\fR or \fB\-p\fR Enable or disable \s-1PAGEEXEC\s0" 4 @@ -211,6 +216,10 @@ eg. \-Pp for \s-1PAGEEXEC\s0, then the default setting \- is used. .IX Item "-F Copy PT_PAX flags to XT_PAX, if possible" .IP "\fB\-f\fR Copy \s-1XT_PAX\s0 flags to \s-1PT_PAX\s0, if possible" 4 .IX Item "-f Copy XT_PAX flags to PT_PAX, if possible" +.IP "\fB\-L\fR Only set \s-1PT_APX\s0 flags, if both are possible" 4 +.IX Item "-L Only set PT_APX flags, if both are possible" +.IP "\fB\-l\fR Only set \s-1XT_PAX\s0 flags, if both are possible" 4 +.IX Item "-l Only set XT_PAX flags, if both are possible" .IP "\fB\-v\fR View the flags" 4 .IX Item "-v View the flags" .IP "\fB\-h\fR Print out a short help message and exit." 4 diff --git a/doc/paxctl-ng.pod b/doc/paxctl-ng.pod index 90aac3d..19a9026 100644 --- a/doc/paxctl-ng.pod +++ b/doc/paxctl-ng.pod @@ -18,6 +18,10 @@ B -F [-v] ELF B -f [-v] ELF +B -L [-v] ELF + +B -l [-v] ELF + B [-h] =head1 DESCRIPTION @@ -44,13 +48,14 @@ Extended Attributes, otherwise these are lost, unlike PT_PAX markings which are carried within the binary itself. B is opportunistic without taking control away from the user. If both -a PT_PAX program header and XT_PAX extended attribute field "user.pax" exist, and -then both markings will be equally updated when the user modifies the flags. If -only one marking exists, then only that marking will be updated. Under no circumstances -will B create a PT_PAX program header. It will attempt to create an XT_PAX -extended attribute field if it is instructed to do so with the -C or -c flag, -and it will attempt to synchronize the PT_PAX and XT_PAX markings if given the -F -or -f flag. +a PT_PAX program header and XT_PAX extended attribute field "user.pax" exist, then +both markings will be equally updated when the user modifies the flags, unless the +B<-L> or B<-l> flags are given, limiting the markigs to just PT_PAX or XT_PAX. If +only one marking is possible, then only that marking will be updated. Under no +circumstances will B create a PT_PAX program header as B does. +It will only attempt to create an XT_PAX extended attribute field if it is instructed +to do so with the -C or -c flag, and it will attempt to synchronize the PT_PAX and +XT_PAX markings if given the B<-F> or B<-f> flag. =head1 OPTIONS @@ -85,6 +90,10 @@ eg. -Pp for PAGEEXEC, then the default setting - is used. =item B<-f> Copy XT_PAX flags to PT_PAX, if possible +=item B<-L> Only set PT_APX flags, if both are possible + +=item B<-l> Only set XT_PAX flags, if both are possible + =item B<-v> View the flags =item B<-h> Print out a short help message and exit.