misc/51612: Minor adjustments to the paxctl(8) man page

[dhgutteridge%sympatico.ca@localhost]

>Number:         51612
>Category:       misc
>Synopsis:       Minor adjustments to the paxctl(8) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 08 03:05:00 +0000 2016
>Originator:     David H. Gutteridge
>Release:        HEAD
>Organization:
>Environment:
n/a
>Description:
The changes are self-evident from the diff, but just in case there
are any questions, here's what's what.

Content:

* The Bugs section referred solely to PaX Segvguard, but there are
other flags available now, so I generalized the statement.
* I've added that any flags stored as ELF notes don't survive the
binary being updated. This is probably obvious to many, but I think
it bears being explicitly mentioned.

>How-To-Repeat:

>Fix:
--- paxctl.8~
+++ paxctl.8	2016-11-07 21:54:07.642529519 -0500
@@ -23,7 +23,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd September 17, 2009
+.Dd November 7, 2016
 .Dt PAXCTL 8
 .Os
 .Sh NAME
@@ -110,8 +110,9 @@
 utility currently uses
 .Xr elf 5
 .Dq note
-sections to mark executables as PaX Segvguard enabled.
+sections to mark executables as having PaX flags enabled.
 This will be done using
 .Xr fileassoc 9
 in the future so that we can control who does the marking and
-not altering the binary file signature.
+not altering the binary file signature. (Note this also means that
+at present any flags set do not survive binary file upgrades.)