* New upstream release, uploaded to Debian. (LP: #530778) (Closes: #570990)
* genpaxtest: Modify so that the 'paxtest' script generated uses
either a user-provided logfile as argument or the $HOME/paxtest.log
instead of paxtest.log for its results in order to prevent it from
writing in the users' CWD and avoid symlink tricks if the user is
executing this in a shared (i.e. writable by others) directory such as
/tmp. Fixes CVE-2010-3373 (Closes: #598413)
* Updated results in the results/ directory for a stock Debian kernel
(i.e. no overflow protection)
* Use debhelper compatibility version 5
* debian/rules: Use conditions to build using 'linux32', 'linux64' or
just 'linux'
* Document the new Homepage in debian/control, also list both the new
and the old one in debian/copyright
* Updated debian/paxtest.sgml to properly reflect the arguments used in the
paxtest script and the new behaviour wrt log files.
* Fix upstream's debian/changelog to have proper maintainer lines. Use the
date information of the files as a basis.
* Updated the content under results/ for a stock Debian kernel (2.6.32)
and rename the older result files for Debian kernel 2.4.25
paxtest (0.9.9-3) stable; urgency=low
* fixed Makefile to use -nopie for Gentoo Hardened on ET_EXEC tests
paxtest (0.9.9-2) stable; urgency=low
* fixed writable text segments test under gcc 4.5 optimizations
paxtest (0.9.9-1) stable; urgency=low
* added SPARC/64 support
* added PPC/64 support (return to function tests should be ignored for PPC64)
* added 32/64bit target support
* added shellode.h to easily support additional architectures
* made paxctl generate the PT_PAX_FLAGS header for binaries that
didn't have one
-- Ubuntu Archive Auto-Sync <email address hidden> Fri, 15 Oct 2010 09:53:22 +0000
This bug was fixed in the package paxtest - 1:0.9.9-1
---------------
paxtest (1:0.9.9-1) unstable; urgency=medium
* New upstream release, uploaded to Debian. (LP: #530778) (Closes: #570990)
* genpaxtest: Modify so that the 'paxtest' script generated uses
either a user-provided logfile as argument or the $HOME/paxtest.log
instead of paxtest.log for its results in order to prevent it from
writing in the users' CWD and avoid symlink tricks if the user is
executing this in a shared (i.e. writable by others) directory such as
/tmp. Fixes CVE-2010-3373 (Closes: #598413)
* Updated results in the results/ directory for a stock Debian kernel
(i.e. no overflow protection)
* Use debhelper compatibility version 5
* debian/rules: Use conditions to build using 'linux32', 'linux64' or
just 'linux'
* Document the new Homepage in debian/control, also list both the new
and the old one in debian/copyright
* Updated debian/paxtest.sgml to properly reflect the arguments used in the
paxtest script and the new behaviour wrt log files.
* Fix upstream's debian/changelog to have proper maintainer lines. Use the
date information of the files as a basis.
* Updated the content under results/ for a stock Debian kernel (2.6.32)
and rename the older result files for Debian kernel 2.4.25
paxtest (0.9.9-3) stable; urgency=low
* fixed Makefile to use -nopie for Gentoo Hardened on ET_EXEC tests
paxtest (0.9.9-2) stable; urgency=low
* fixed writable text segments test under gcc 4.5 optimizations
paxtest (0.9.9-1) stable; urgency=low
* added SPARC/64 support
* added PPC/64 support (return to function tests should be ignored for PPC64)
* added 32/64bit target support
* added shellode.h to easily support additional architectures
* made paxctl generate the PT_PAX_FLAGS header for binaries that
didn't have one
-- Ubuntu Archive Auto-Sync <email address hidden> Fri, 15 Oct 2010 09:53:22 +0000