| 1 |
Hi, |
| 2 |
|
| 3 |
On 09:41 Wed 10 Nov , Christopher Schwan wrote: |
| 4 |
> I followed the instructions listed in number 6 of the following page: |
| 5 |
> http://www.gentoo.org/proj/en/hardened/gnu-stack.xml . However, the fix is |
| 6 |
> incomplete (some architectures still have executable stacks) and I had some |
| 7 |
> problems with BASH: |
| 8 |
> |
| 9 |
> for i in $(find . -type f -name '*.asm') ; do |
| 10 |
> echo $i >/dev/null |
| 11 |
> cat >> $i <<-EOF |
| 12 |
> #if defined(__linux__) && defined(__ELF__) |
| 13 |
> .section .note.GNU-stack,"",%progbits |
| 14 |
> #endif |
| 15 |
> EOF |
| 16 |
> done |
| 17 |
> |
| 18 |
> If I remove the line with "echo" (which *should* be completely useless), the |
| 19 |
> cat command does not patch files - WHY ?! Also, mpir seemed to have dropped |
| 20 |
> yasm beginning with mpir-2.1 (?), so I think at least one loop in mpir's |
| 21 |
> ebuild is superfluous. |
| 22 |
|
| 23 |
I will look into this. What is the state for ppc and prefix ? In |
| 24 |
short: What keywords should we have on mpir? I can only test ~amd64 and |
| 25 |
~x86. |
| 26 |
|
| 27 |
> > There are talk on sage-devel which is very close to mpir upstream |
| 28 |
> > to take a different approach: using an m4 macro and a linker flag |
| 29 |
> > to remove them -Wl,-z,noexecstack. |
| 30 |
> |
| 31 |
> This seems to be a better idea. |
| 32 |
|
| 33 |
Will that be available anytime soon? |
| 34 |
|
| 35 |
Cheers, |
| 36 |
Thomas |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Thomas Kahle |
| 42 |
http://dev.gentoo.org/~tomka/ |
Archives