| 1 |
solar |
1.1 |
# ChangeLog for sys-apps/paxctl
|
| 2 |
dostrow |
1.7 |
# Copyright 2000-2005 Gentoo Foundation; Distributed under the GPL v2
|
| 3 |
kevquinn |
1.11 |
# $Header: /var/cvsroot/gentoo-x86/sys-apps/paxctl/ChangeLog,v 1.10 2005/06/11 00:53:54 solar Exp $
|
| 4 |
|
|
|
| 5 |
|
|
*paxctl-0.3-r1 (13 Jun 2005)
|
| 6 |
|
|
|
| 7 |
|
|
13 Jun 2005; Kevin F. Quinn <kevquinn@gentoo.org>
|
| 8 |
|
|
+files/paxctl-0.3-error-codes.patch, +paxctl-0.3-r1.ebuild:
|
| 9 |
|
|
- return EXIT_FAILURE when paxctl fails to do as requested
|
| 10 |
solar |
1.10 |
|
| 11 |
|
|
10 Jun 2005; <solar@gentoo.org> paxctl-0.3.ebuild:
|
| 12 |
|
|
- stable on x86/ppc/amd64
|
| 13 |
solar |
1.9 |
|
| 14 |
|
|
*paxctl-0.3 (03 May 2005)
|
| 15 |
|
|
|
| 16 |
|
|
03 May 2005; <solar@gentoo.org> +paxctl-0.3.ebuild:
|
| 17 |
|
|
- new paxctl release. new version includes ability to reuse/rename existing
|
| 18 |
|
|
unneeded program header into PT_PAX_FLAGS
|
| 19 |
agriffis |
1.8 |
|
| 20 |
|
|
01 Apr 2005; Aron Griffis <agriffis@gentoo.org> paxctl-0.2.ebuild:
|
| 21 |
|
|
stable on ia64
|
| 22 |
dostrow |
1.7 |
|
| 23 |
|
|
17 Mar 2005; Daniel Ostrow <dostrow@gentoo.org> paxctl-0.2.ebuild:
|
| 24 |
|
|
~ppc64 for testing
|
| 25 |
solar |
1.6 |
|
| 26 |
|
|
22 Jul 2004; <solar@gentoo.org> paxctl-0.2.ebuild:
|
| 27 |
|
|
marked paxctl stable on x86 now that min-version binutils is in stable
|
| 28 |
lv |
1.5 |
|
| 29 |
|
|
21 Jul 2004; Travis Tilley <lv@gentoo.org> paxctl-0.2.ebuild:
|
| 30 |
|
|
stable on amd64
|
| 31 |
agriffis |
1.4 |
|
| 32 |
|
|
30 Jun 2004; Aron Griffis <agriffis@gentoo.org> paxctl-0.2.ebuild:
|
| 33 |
|
|
sync IUSE (missing), glibc -> libc
|
| 34 |
aliz |
1.2 |
|
| 35 |
|
|
*paxctl-0.2 (18 Feb 2004)
|
| 36 |
solar |
1.1 |
|
| 37 |
|
|
18 Feb 2004; <solar@gentoo.org> :
|
| 38 |
|
|
This is paxctl for controlling PaX flags on a per binary basis. PaX
|
| 39 |
|
|
is an intrusion prevention system that provides the best protection
|
| 40 |
|
|
mechanisms against memory corruption bugs. Some applications are not
|
| 41 |
|
|
compatible with certain features (due to design or bad engineering)
|
| 42 |
|
|
and therefore they have to be exempted from certain enforcements. It
|
| 43 |
|
|
is also possible to use PaX in soft mode where none of the protection
|
| 44 |
|
|
mechanisms are active by default - here paxctl can be used to turn
|
| 45 |
|
|
them on for selected programs (e.g., network daemons, programs that
|
| 46 |
|
|
process network data such as mail clients, web browsers, etc).
|
| 47 |
|
|
|
| 48 |
|
|
PaX and paxctl work on ELF executables, both of the standard ET_EXEC
|
| 49 |
|
|
and the newer ET_DYN kind (older PaX releases referred to the latter
|
| 50 |
|
|
as ET_DYN executables, these days they are called Position Independent
|
| 51 |
|
|
Executables or PIEs for short).
|
| 52 |
|
|
|
Parent Directory
| 
Revision Log