Timeline for How to chmod without /usr/bin/chmod?
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 22, 2016 at 6:09 | history | suggested | user12345 | CC BY-SA 3.0 |
/lib64/ is where you will find the loader on a 64-bit system. This change brings what many users already have left comments about into the answer itself. The other characters removed were superfluous and useful to get past the 6 char limit.
|
| Mar 22, 2016 at 5:46 | review | Suggested edits | |||
| S Mar 22, 2016 at 6:09 | |||||
| Sep 12, 2014 at 3:45 | comment | added | lepe | /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 , /lib64/ld-linux-x86-64.so.2 are other path alternatives. If not, use "locate ld-linux" to find it out. | |
| Jun 19, 2014 at 14:39 | comment | added | Unnikrishnan | That one was brilliant man :) | |
| Mar 14, 2014 at 18:19 | comment | added | Andres Riofrio | @MichaelKjörling I think it's because I was trying to execute another program in /tmp using this technique. | |
| Mar 14, 2014 at 12:27 | comment | added | user |
@AndresRiofrio Why on Earth would /, /lib, /bin or /usr/bin be mounted noexec? Your linked question is about /tmp which is a different beast entirely.
|
|
| Jul 26, 2013 at 8:04 | comment | added | Andres Riofrio | This doesn't work if the filesystem is mounted with noexec. As it should! | |
| Jul 22, 2013 at 17:43 | comment | added | Sverre Rabbelier | @Rotsor I believe NixOS actually has to do something to each binary to use the right linker paths, instead of the hardcoded one. | |
| Jul 22, 2013 at 15:17 | comment | added | Rotsor |
@JonathanCallen, not true. NixOS is an example of a Linux-based OS distribution where directories /lib and /lib64 do not even exist.
|
|
| Jul 22, 2013 at 14:15 | comment | added | anon |
What would happen if you chmod'd ld-linux.so?
|
|
| Jul 22, 2013 at 13:18 | comment | added | Thorbjørn Ravn Andersen | Note: this is for Linux, not Ubix in general. | |
| Jul 22, 2013 at 10:00 | comment | added | Janos Pasztor | @gerrit If everything gets the execution bit unset, you reboot the system with a live CD and reset the permissions. However, in that case it's probably easier to just reinstall the whole system since who knows what has been borked in the process. | |
| Jul 22, 2013 at 9:55 | comment | added | gerrit | What if those too get their execution bit unset? | |
| Jul 22, 2013 at 3:54 | comment | added | slm♦ | You hit a homerun with this answer 8-). | |
| Jul 22, 2013 at 2:43 | comment | added | Jonathan Callen |
On x86 (32-bit) Linux, the dynamic linker must be at exactly the path /lib/ld-linux.so.2, on x86-64 (64-bit) Linux, the dynamic linker must be at exactly the path /lib64/ld-linux-x86-64.so.2. Both of these are normally symlinks to the correct file, but that exact path is required to be present.
|
|
| Jul 21, 2013 at 20:43 | comment | added | Bratchley |
minor correction: 64 bit libraries are usually under /lib64
|
|
| Jul 21, 2013 at 19:33 | comment | added | Sundar R | Thanks. What permissions does ld-linux.so itself have? (I have only cygwin and it doesn't seem to have this file.) Is this an easy way to override the executable permission bit then? | |
| Jul 21, 2013 at 19:24 | comment | added | EightBitTony | I love any day where I learn something new. | |
| Jul 21, 2013 at 19:23 | history | answered | Michael Mrozek | CC BY-SA 3.0 |