Linked by Thom Holwerda on Wed 9th Nov 2011 21:26 UTC, submitted by edwin
Thread beginning with comment 496954
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-05-06
I'll take being able to easily fix everything with easily being able to break everything every time over not able to fix anything.
The LD_LIBRARY_PATH suid root binary security hole is one that if you know about you can avoid. It's not something that means throw the whole system out.
Update: Looks it's protected against anyway.
http://en.wikipedia.org/wiki/Setuid
"The invoking user will be prohibited by the system from altering the new process in any way, such as by using ptrace, LD_LIBRARY_PATH or sending signals to it"
Edited 2011-11-11 11:43 UTC