Your message dated Tue, 12 May 2015 15:45:21 +0200
with message-id <[email protected]>
and subject line Re: [Ceph-maintainers] Bug#784882: Bug#784882: librados2:
should not request an executable stack
has caused the Debian Bug report #784882,
regarding librados2: should not request an executable stack
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
784882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784882
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: librados2
Version: 0.80.7-2
Severity: normal
# execstack /usr/lib/x86_64-linux-gnu/librados.so.2
X /usr/lib/x86_64-linux-gnu/librados.so.2
librados currently requests an executable stack. It would be ideal if it
didn't request such access so that programs such as /usr/bin/qemu-system-i386
that link against it are less vulnerable to stack based attacks.
Does librados even need an executable stack? In a quick test it appeared to
work without it.
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages librados2 depends on:
ii libboost-system1.55.0 1.55.0+dfsg-3
ii libboost-thread1.55.0 1.55.0+dfsg-3
ii libc6 2.19-18
ii libgcc1 1:4.9.2-10
ii libnspr4 2:4.10.7-1
ii libnss3 2:3.17.2-1.1
ii libstdc++6 4.9.2-10
ii libuuid1 2.25.2-6
ii multiarch-support 2.19-18
librados2 recommends no packages.
librados2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.80.9-1
Gregory Farnum <[email protected]> writes:
> This is resolved upstream. See the ticket at
> http://tracker.ceph.com/issues/10114; the original fix for upstream
> master is commit 06a245a9845c0c126fb3106b41b2fd2bc4bc4df3, and it is
> in the firefly (v0.80.* releases) as commit
> 01faf1356f648ded9acda02e7cc67c1adb9e9ee3 from November 14 2014 (this
> is in v0.80.9 at least, not sure what the timing is on the previous
> releases).
I just verified that this is indeed fixed in 0.80.9-1 recently uploaded
to unstable. If the stable release team agrees (see #784373) we will
soon have this fixed even in stable.
Gaudenz
> -Greg
>
> On Sat, May 9, 2015 at 8:03 PM, Russell Coker <[email protected]> wrote:
>> Package: librados2
>> Version: 0.80.7-2
>> Severity: normal
>>
>> # execstack /usr/lib/x86_64-linux-gnu/librados.so.2
>> X /usr/lib/x86_64-linux-gnu/librados.so.2
>>
>> librados currently requests an executable stack. It would be ideal if it
>> didn't request such access so that programs such as /usr/bin/qemu-system-i386
>> that link against it are less vulnerable to stack based attacks.
>>
>> Does librados even need an executable stack? In a quick test it appeared to
>> work without it.
>>
>> -- System Information:
>> Debian Release: 8.0
>> APT prefers stable-updates
>> APT policy: (500, 'stable-updates'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
>> Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages librados2 depends on:
>> ii libboost-system1.55.0 1.55.0+dfsg-3
>> ii libboost-thread1.55.0 1.55.0+dfsg-3
>> ii libc6 2.19-18
>> ii libgcc1 1:4.9.2-10
>> ii libnspr4 2:4.10.7-1
>> ii libnss3 2:3.17.2-1.1
>> ii libstdc++6 4.9.2-10
>> ii libuuid1 2.25.2-6
>> ii multiarch-support 2.19-18
>>
>> librados2 recommends no packages.
>>
>> librados2 suggests no packages.
>>
>> -- no debconf information
>> _______________________________________________
>> Ceph-maintainers mailing list
>> [email protected]
>> http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
> _______________________________________________
> Ceph-maintainers mailing list
> [email protected]
> http://lists.ceph.com/listinfo.cgi/ceph-maintainers-ceph.com
--- End Message ---
