| 1 |
On Thu, 2006-04-13 at 15:35 +0200, pageexec@××××××××.hu wrote: |
| 2 |
> On 13 Apr 2006 at 14:46, Mivz wrote: |
| 3 |
> > Without enforcing ping works just fine: |
| 4 |
> |
| 5 |
> this is good enough to tell the story. |
| 6 |
|
| 7 |
If you are unable to fix the text relocations, you can label the library |
| 8 |
appropriately as texrel_shlib_t. |
| 9 |
|
| 10 |
chcon -t texrel_shlib_t foo.so |
| 11 |
|
| 12 |
> > brk(0) = 0x8001e320 |
| 13 |
> |
| 14 |
> that address looks interesting, you'll see why. |
| 15 |
> |
| 16 |
> |
| 17 |
> > mprotect(0x80000000, 40960, PROT_READ|PROT_WRITE) = 0 |
| 18 |
> > mprotect(0x80000000, 40960, PROT_READ|PROT_EXEC) = 0 |
| 19 |
> |
| 20 |
> and this is where the PROT_WRITE->PROT_EXEC transition happens, |
| 21 |
> a strong indication of text relocations. comparing it to the |
| 22 |
> above brk address, we can be quite sure that it is in fact the |
| 23 |
> main application itself being subject to such torture (brk always |
| 24 |
> follows the main app in memory). noting the unusual start address |
| 25 |
> of the main app (it'd be 0x08048000 for ET_EXEC), we can conclude |
| 26 |
> that your ping executable is a PIE that is not fully PIC. run |
| 27 |
> scanelf -T on it to see where the problem is. |
| 28 |
|
| 29 |
-- |
| 30 |
Chris PeBenito |
| 31 |
<pebenito@g.o> |
| 32 |
Developer, |
| 33 |
Hardened Gentoo Linux |
| 34 |
Embedded Gentoo Linux |
| 35 |
|
| 36 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243 |
| 37 |
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243 |
Archives