| 1 |
On 28 May 2013 at 21:29, Anthony G. Basile wrote: |
| 2 |
|
| 3 |
> Unfortunately it is very difficult to find everything that links against |
| 4 |
> everything on a system. First there's just a simple logistic problem, |
| 5 |
> going through all ELF on a system and running ldd (or readelf -d) is |
| 6 |
> time consuming and likely to miss stuff. On gentoo with portage (not |
| 7 |
> paludis!) we have linkage info in NEEDED.ELF.2 in vdb created at build |
| 8 |
> time by examing linkage info, but this also can't be everything. |
| 9 |
> Consider plugins that dlopen-ed at runtime. |
| 10 |
|
| 11 |
PaX already has code for textrel handling where it looks at mapped libraries, |
| 12 |
it'd be easy to add detection for mismatched process vs. library PaX flags |
| 13 |
at the same time. |
| 14 |
|
| 15 |
let me know if you could use this (users would have to send you logs so that |
| 16 |
you can build a database or perhaps some tool run locally could do it for |
| 17 |
everyone) and i'll code it up. |
| 18 |
|
| 19 |
> That's not what's happening there. No XATTR_PAX flags implies the |
| 20 |
> default markings which is "-e---". |
| 21 |
|
| 22 |
actually no pax.flags xattr on the file means that it'll be ignored and |
| 23 |
the other mechanisms will be used (which can ultimately be -e--- if no |
| 24 |
other mechanism is configured). now what you do in paxctl-ng is another |
| 25 |
matter, i thought that it'd keep these two flags in sync, at least when |
| 26 |
an already existing PT_PAX one is not the default value like it wasn't |
| 27 |
in his case (EMUTRAMP was on for softmode). |
Archives