Bug 686817

Summary: forbid creating hard links to foreign objects
Product: [openSUSE] openSUSE 11.4 Reporter: Christopher Yeleighton <giecrilj>
Component: BasesystemAssignee: Philipp Thomas <pth>
Status: VERIFIED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P4 - Low    
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.4   
URL: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8117
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Christopher Yeleighton 2011-04-12 07:22:13 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0

An operator should not be allowed to create hard links to foreign objects in a sticky directory it cannot unconditionally write to (drwxrwxrwt) because she has to ask the object’s owner to remove them afterwards.  

In other words, the operator should be able to undo every operation she performs, (with hardware permitting and suid operations excepted).

Reproducible: Always

Steps to Reproduce:
  1. { cd /tmp && ln /bin/ls ls && rm ls; }

Actual Results:  
  1. rm: operation not permitted

Expected Results:  
  1. ln: operation not permitted

Coreutils bug#8117 (INVALID).
Comment 1 Philipp Thomas 2011-07-05 16:14:05 UTC
Please report this upstream by sending a mail to bug-coreutils@gnu.org. This is nothing we would implement ourselves.
Comment 2 Christopher Yeleighton 2011-07-06 10:17:16 UTC
Quoting the closing upstream:

<**
Yes this is true.  But this doesn't have anything to do with either
'ln' or 'rm' but is instead a behavior associated with Unix
filesystems and specifically the behavior of the sticky-bit on
directories.  It is an operating system policy.  Therefore I am
tagging this as not a bug in the bug tracking system.
**>

I understand that openSUSE may have nothing to do with it; I reopen this bug because it turns out upstream has been mis-identified.
Comment 3 Philipp Thomas 2011-07-06 10:47:37 UTC
Then figure out yourself where upstream could be! As it looks you probably should bring this up with the POSIX folks.