sys-apps/paxctl/ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# ChangeLog for sys-apps/paxctl
# Copyright 2000-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/sys-apps/paxctl/ChangeLog,v 1.12 2005/08/23 20:27:14 agriffis Exp $

  23 Aug 2005; Aron Griffis <agriffis@gentoo.org> paxctl-0.3.ebuild:
  stable on ia64

*paxctl-0.3-r1 (13 Jun 2005)

  13 Jun 2005; Kevin F. Quinn <kevquinn@gentoo.org>
  +files/paxctl-0.3-error-codes.patch, +paxctl-0.3-r1.ebuild:
  - return EXIT_FAILURE when paxctl fails to do as requested

  10 Jun 2005; <solar@gentoo.org> paxctl-0.3.ebuild:
  - stable on x86/ppc/amd64

*paxctl-0.3 (03 May 2005)

  03 May 2005; <solar@gentoo.org> +paxctl-0.3.ebuild:
  - new paxctl release. new version includes ability to reuse/rename existing
  unneeded program header into PT_PAX_FLAGS

  01 Apr 2005; Aron Griffis <agriffis@gentoo.org> paxctl-0.2.ebuild:
  stable on ia64

  17 Mar 2005; Daniel Ostrow <dostrow@gentoo.org> paxctl-0.2.ebuild:
  ~ppc64 for testing

  22 Jul 2004; <solar@gentoo.org> paxctl-0.2.ebuild:
  marked paxctl stable on x86 now that min-version binutils is in stable

  21 Jul 2004; Travis Tilley <lv@gentoo.org> paxctl-0.2.ebuild:
  stable on amd64

  30 Jun 2004; Aron Griffis <agriffis@gentoo.org> paxctl-0.2.ebuild:
  sync IUSE (missing), glibc -> libc

*paxctl-0.2 (18 Feb 2004)

  18 Feb 2004; <solar@gentoo.org> :
  This is paxctl for controlling PaX flags on a per binary basis. PaX
  is an intrusion prevention system that provides the best protection
  mechanisms against memory corruption bugs. Some applications are not
  compatible with certain features (due to design or bad engineering)
  and therefore they have to be exempted from certain enforcements. It
  is also possible to use PaX in soft mode where none of the protection
  mechanisms are active by default - here paxctl can be used to turn
  them on for selected programs (e.g., network daemons, programs that
  process network data such as mail clients, web browsers, etc).
  
  PaX and paxctl work on ELF executables, both of the standard ET_EXEC
  and the newer ET_DYN kind (older PaX releases referred to the latter
  as ET_DYN executables, these days they are called Position Independent
  Executables or PIEs for short).