| 1 |
Switching to the upgraded kernel fixed the issue. My guess so far is |
| 2 |
that I somehow messed with that library when I was dinking around with |
| 3 |
my kernel sources, which in turn affected the trust relationship with |
| 4 |
grsec. |
| 5 |
|
| 6 |
On 1/10/07, pageexec@××××××××.hu <pageexec@××××××××.hu> wrote: |
| 7 |
> On 9 Jan 2007 at 5:53, Matt Poletiek wrote: |
| 8 |
> |
| 9 |
> > I was upgrading my kernel/patching it with grsec the other day when |
| 10 |
> > all of a sudden I couldnt su as a normal user anymore. I dont know how |
| 11 |
> > this would apply considering the new kernel wasnt (and still isnt) |
| 12 |
> > booted yet. |
| 13 |
> |
| 14 |
> given that the logs come from grsec, you must have been already running |
| 15 |
> such a kernel. |
| 16 |
> |
| 17 |
> > grsec: denied untrusted exec of /lib64/ld-2.4.so by /bin/su[su:31770] |
| 18 |
> |
| 19 |
> check the access rights on /lib64/ld-2.4.so, they apparently violate |
| 20 |
> the TPE rules. |
| 21 |
> |
| 22 |
> > How do these relate? What is ld-2.4.so? Whats so bad about it? |
| 23 |
> |
| 24 |
> it's the 64 bit dynamic linker (part of glibc). |
| 25 |
> |
| 26 |
> -- |
| 27 |
> gentoo-hardened@g.o mailing list |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Matthew Poletiek |
| 34 |
www.chill-fu.net |
| 35 |
-- |
| 36 |
gentoo-hardened@g.o mailing list |
Archives