86da4a5eea
instead of removing the file and issue a warning about the removal, do not do any operation at all in case -P is specified when the dinode has hard links. With -f and -P specified together, we assume that the user wants rm to overwrite the contents of the file and remove it (destroy the contents of file but leave its hard links as is). The reason of doing it this way is that, in case where a hard link is created by a malicious user (currently this is permitted even if the user has no access to the file). Losing the link can potentially mean that the actual owner would lose control completely to the user who wants to obtain access in a future day. Discussed with: Peter Jermey |
||
|---|---|---|
| .. | ||
| cat | ||
| chflags | ||
| chio | ||
| chmod | ||
| cp | ||
| csh | ||
| date | ||
| dd | ||
| df | ||
| domainname | ||
| echo | ||
| ed | ||
| expr | ||
| getfacl | ||
| hostname | ||
| kenv | ||
| kill | ||
| ln | ||
| ls | ||
| mkdir | ||
| mv | ||
| pax | ||
| ps | ||
| pwd | ||
| rcp | ||
| realpath | ||
| rm | ||
| rmail | ||
| rmdir | ||
| setfacl | ||
| sh | ||
| sleep | ||
| stty | ||
| sync | ||
| test | ||
| uuidgen | ||
| Makefile | ||
| Makefile.inc | ||