<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>114733</bug_id>
          
          <creation_ts>2005-12-07 04:21 0000</creation_ts>
          <short_desc>games-fps/ut2004 fails FEATURES=&quot;stricter&quot; tests</short_desc>
          <delta_ts>2005-12-14 12:54:37 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Games</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>UPSTREAM</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>betelgeuse@gentoo.org</reporter>
          <assigned_to>games@gentoo.org</assigned_to>
          <cc>ana_a_m_@hotmail.com</cc>
    
    <cc>ryan@epicgames.com</cc>

      

      
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2005-12-07 04:21:26 0000</bug_when>
            <thetext>&gt;&gt;&gt; Install ut2004-3369 into /var/tmp/portage/ut2004-3369/image/ category games-fps
man:
scanelf: rpath_security_checks(): Security problem with relative RPATH &apos;.&apos; in
/var/tmp/portage/ut2004-3369/image//opt/ut2004/System/ut2004-bin

QA Notice: the following files contain executable stacks
 Files with executable stacks will not work properly (or at all!)
 on some architectures/operating systems.  A bug should be filed
 at http://bugs.gentoo.org/ to make sure the file is fixed.
RWX --- --- opt/ut2004/System/ucc-bin
RWX --- --- opt/ut2004/System/ut2004-bin

&gt;&gt;&gt; Completed installing ut2004-3369 into /var/tmp/portage/ut2004-3369/image/

As this is a binary package please work with upstream to get this fixed.
http://www.gentoo.org/proj/en/hardened/gnu-stack.xml

Portage 2.0.53 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r3,
2.6.14-gentoo-r4 i686)
=================================================================
System uname: 2.6.14-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.12.0_pre11
ccache version 2.4 [enabled]
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r1
sys-devel/libtool:   1.5.20-r1
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS=&quot;x86 ~x86&quot;
AUTOCLEAN=&quot;yes&quot;
CBUILD=&quot;i686-pc-linux-gnu&quot;
CFLAGS=&quot;-O2 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer&quot;
CHOST=&quot;i686-pc-linux-gnu&quot;
CONFIG_PROTECT=&quot;/etc /usr/kde/2/share/config /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config
/usr/share/X11/xkb /usr/share/config /var/qmail/control&quot;
CONFIG_PROTECT_MASK=&quot;/etc/env.d/java/ /etc/gconf /etc/init.d
/etc/java-config/vms/ /etc/splash /etc/terminfo /etc/env.d&quot;
CXXFLAGS=&quot;-O2 -march=pentium4 -pipe -mfpmath=sse -ffast-math -fomit-frame-pointer&quot;
DISTDIR=&quot;/usr/src/distfiles&quot;
FEATURES=&quot;autoaddcvs autoconfig ccache collision-protect cvs distlocks
fixpackages sandbox sfperms sign strict stricter verify-rdepend&quot;
GENTOO_MIRRORS=&quot; http://trumpetti.atm.tut.fi/gentoo 
http://lame.lut.fi/linux/gentoo &quot;
LANG=&quot;en_US.utf8&quot;
LC_ALL=&quot;en_US.utf8&quot;
LINGUAS=&quot;fi&quot;
MAKEOPTS=&quot;-j2 &quot;
PKGDIR=&quot;/home/pkg/&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR=&quot;/usr/portage&quot;
PORTDIR_OVERLAY=&quot;/mnt/checkouts/overlays/betelgeuse /mnt/checkouts/overlays/axxo&quot;
SYNC=&quot;rsync://rsync.gentoo.org/gentoo-portage&quot;
USE=&quot;x86 aac acl acpi alsa apm arts audiofile avi bash-completion berkdb
bitmap-fonts bluetooth browserplugin bzip2 bzlib cdb cddb cdparanoia cdr crypt
cups dbus divx4linux dts dvd dvdr dvdread emboss esd expat fam ffmpeg firefox
foomaticdb freetype gif glut gstreamer gtk2 hal idn java jpeg kde kdeenablefinal
lcms libg++ libwww logitech-mouse mad makecheck mikmod mjpeg mmx mmx2 mng mp3
mpeg ncurses network nptl nptlonly nsplugin nvidia offensive ogg oggvorbis
opengl pam pcre pdflib png qt quicktime readline real rtc ruby samba spell sse
sse2 ssl subversion svg symlink tcpd theora tiff truetype truetype-fonts
type1-fonts udev unicode usb userlocales vorbis win32codecs xine xml xml2 xv
xvid zlib video_cards_nvidia linguas_fi userland_GNU kernel_linux elibc_glibc&quot;
Unset:  ASFLAGS, CTARGET, LDFLAGS</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-07 05:12:03 0000</bug_when>
            <thetext>I&apos;ll talk to upstream but I am very confident that this will be a WONTFIX on
their end and CANTFIX on ours.  This will be even more of an issue if you start
going into the older Loki games, since there is no more upstream to talk with in
existence.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-07 07:09:44 0000</bug_when>
            <thetext>*** Bug 114748 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-07 07:28:46 0000</bug_when>
            <thetext>Ryan, can you look into this?  I can file a bug on the icculus.org bugzilla if
you would prefer.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ryan@epicgames.com</who>
            <bug_when>2005-12-07 11:24:15 0000</bug_when>
            <thetext>
I&apos;m not sure where it&apos;s picking up the idea that ut2004 needs an executable
stack (to my knowledge, we don&apos;t). Is there some way to pick out what part of
the binary or the build process is causing this?

Is there some way to just flag an existing ELF binary as &quot;doesn&apos;t really need
executable stack&quot;? I&apos;d like that heaps better than altering the existing build
process, if possible.

--ryan.

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2005-12-07 12:18:20 0000</bug_when>
            <thetext>(In reply to comment #4)
&gt; I&apos;m not sure where it&apos;s picking up the idea that ut2004 needs an executable
&gt; stack (to my knowledge, we don&apos;t). Is there some way to pick out what part of
&gt; the binary or the build process is causing this?
&gt; 

Please read the link I already gave you:
http://www.gentoo.org/proj/en/hardened/gnu-stack.xml</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-12-07 15:45:31 0000</bug_when>
            <thetext>if havent updated the docs or made a new release since i added the functionality
yesterday, but i updated the `scanelf` util to look for object files which do
not contain the .note.GNU-stack section ... such object files would cause the
final binary to contain an executable stack

i&apos;ll post back when ive done so</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ryan@epicgames.com</who>
            <bug_when>2005-12-07 17:38:27 0000</bug_when>
            <thetext> 
&gt; Please read the link I already gave you:
&gt; http://www.gentoo.org/proj/en/hardened/gnu-stack.xml

Whoops, I missed that, sorry. I&apos;ll read that now.

--ryan.

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-12-07 20:33:23 0000</bug_when>
            <thetext>ok, ive updated the gnu stack docs ...

just grab the 0.1.5 tarball of pax-utils:
http://dev.gentoo.org/~vapier/dist/pax-utils-0.1.5.tar.bz2

and then run `scanelf -qeR &lt;path to compiled ut2004 source code&gt;`

it should help you locate the offending object files quickly</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-13 13:38:14 0000</bug_when>
            <thetext>The new 3369-r1 version no longer fails.  It still contains the relative RPATH,
but it isn&apos;t an error.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2005-12-13 16:21:34 0000</bug_when>
            <thetext>(In reply to comment #9)
&gt; The new 3369-r1 version no longer fails.  It still contains the relative RPATH,
&gt; but it isn&apos;t an error.

QA Notice: the following files contain executable stacks
 Files with executable stacks will not work properly (or at all!)
 on some architectures/operating systems.  A bug should be filed
 at http://bugs.gentoo.org/ to make sure the file is fixed.
RWX --- --- opt/ut2004/System/ucc-bin
RWX --- --- opt/ut2004/System/ut2004-bin


!!! ERROR: games-fps/ut2004-3369-r1 failed.
!!! Function dyn_install, Line 1102, Exitcode 0
!!! Aborting due to +x stack
!!! If you need support, post the topmost build error, NOT this status message.

Do you have pax-utils emerged?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-14 06:03:46 0000</bug_when>
            <thetext>Does portage not pull it in as a dependency?

Anyway, I cannot fix this.  It is a binary application.  Ryan is aware of the
issue.  If he fixes it, great, if not, there&apos;s nothing that I can do about it.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2005-12-14 06:33:31 0000</bug_when>
            <thetext>(In reply to comment #11)
&gt; Does portage not pull it in as a dependency?

2.0.54 will have it.

&gt; Anyway, I cannot fix this.  It is a binary application.  Ryan is aware of the
&gt; issue.  If he fixes it, great, if not, there&apos;s nothing that I can do about it.

The approapriate resolution is upstream then. Reopening to change.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2005-12-14 06:34:09 0000</bug_when>
            <thetext>Being a binary application we need upstream to resolve this issue.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-14 07:31:29 0000</bug_when>
            <thetext>Ryan:  I realized where the confusion came between myself and Petteri.  I run
amd64.  He runs x86.  On amd64, there are no problems.  The problems only
manifest on x86, which leads me to think that by default the compiler/linker on
amd64 fixes this issue for you.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-14 07:32:05 0000</bug_when>
            <thetext>Should I file a bug with your bugzilla for this or is this still sufficient?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wolf31o2@gentoo.org</who>
            <bug_when>2005-12-14 12:52:21 0000</bug_when>
            <thetext>&lt;wolf31o2-work&gt; icculus: you see my latest responses on that executable stack bug?
&lt;icculus&gt; wolf31o2-work: I did, and we might have a problem
&lt;wolf31o2-work&gt; icculus: ok
&lt;icculus&gt; wolf31o2-work: The 32-bit version uses Pixomatic
&lt;icculus&gt; wolf31o2-work: which is not only a big pile of self-modifying
assembly, it&apos;s (ahem) actually a win32 .obj file.
&lt;icculus&gt; I don&apos;t know if it actually executes from the stack, but I can&apos;t flag
it as safe.

Unfortunately, it doesn&apos;t look like we can really fix this.  I&apos;m making comments
to such in the ebuild.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-12-14 12:54:37 0000</bug_when>
            <thetext>no need to put comments in the ebuild

just put RESTRICT=stricter ... that means we&apos;ve analyzed the package and found
it to be not fixable from our standpoint

portage will still bitch about the situation, but it wont abort</thetext>
          </long_desc>
      
    </bug>

</bugzilla>