| 1 |
BTW: |
| 2 |
What is the current state of xt_pax compared to the initial announcement? |
| 3 |
http://archives.gentoo.org/gentoo-dev/msg_4fc5b8e2bdd09f7394b23b44d944c4d7.xml |
| 4 |
I see the new USE flag for hardened-sources. What should I expect upon |
| 5 |
enabling it on a regular hardened system? |
| 6 |
Can I help with testing? If yes: what should I do? |
| 7 |
|
| 8 |
Regards: |
| 9 |
Dw. |
| 10 |
-- |
| 11 |
dr Tóth Attila, Radiológus, 06-20-825-8057 |
| 12 |
Attila Toth MD, Radiologist, +36-20-825-8057 |
| 13 |
|
| 14 |
2012.Március 29.(Cs) 21:52 időpontban PaX Team ezt írta: |
| 15 |
> On 30 Mar 2012 at 20:12, wrote: |
| 16 |
> |
| 17 |
>> On Thu, 29 Mar 2012, Sven Vermeulen wrote: |
| 18 |
>> |
| 19 |
>> >You can try to make it a valid ELF header first, and then paxmark it. |
| 20 |
>> > |
| 21 |
>> >I have the following for my Skype: |
| 22 |
>> >paxctl -C /opt/skype/skype |
| 23 |
>> >paxctl -me /opt/skype/skype |
| 24 |
>> |
| 25 |
>> I tried running paxctl -Cm on it (should be ran on install with |
| 26 |
>> pax_kernel USE |
| 27 |
>> flag), by it still reports an invalid ELF executable. |
| 28 |
> |
| 29 |
> because it is an invalid ELF (it reports sections headers but it doesn't |
| 30 |
> seem to |
| 31 |
> have any, or at least not where the ELF header says they should be). |
| 32 |
> paxctl is not |
| 33 |
> the only one that complains, try readelf or eu-elflint for similar |
| 34 |
> results. |
| 35 |
> |
| 36 |
> as for the solution, you can try out the xattr control method that was |
| 37 |
> written for |
| 38 |
> cases like this. |
| 39 |
> |
| 40 |
> |
| 41 |
> |
Archives