<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: allow cp -p to keep owner in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209261#M32730</link>
    <description>&amp;gt; disk quota not enabled&lt;BR /&gt;&lt;BR /&gt;That does not make it a good idea to let "a&lt;BR /&gt;standard user" create files which some other&lt;BR /&gt;user owns.  It's only one of the reasons, not&lt;BR /&gt;the only reason.  For another example,&lt;BR /&gt;consider a file with rw-r--r-- permissions.&lt;BR /&gt;After you create it, if someone else owns it,&lt;BR /&gt;how do you delete it?  You don't have&lt;BR /&gt;permission to delete it, and you don't have&lt;BR /&gt;permission to change its permissions.&lt;BR /&gt;Allowing this would not be wise.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; here the results:&lt;BR /&gt;&lt;BR /&gt;I want to see where this works "ok" on an&lt;BR /&gt;"HP-UX 11i" system.  (And what, exactly, is&lt;BR /&gt;"HP-UX 11i"?  Show "uname -a" output.)</description>
    <pubDate>Tue, 03 Jun 2008 01:33:50 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2008-06-03T01:33:50Z</dc:date>
    <item>
      <title>allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209256#M32725</link>
      <description>hello,&lt;BR /&gt;I'm looking if there is a way to allow a standard user when copies a file with cp-p to keep the original file owner. It's ok with HP-UX 11i machines and this command works as I wrote, with REHL box don't. Even with local or nfs file systems.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;bests&lt;BR /&gt;Romano</description>
      <pubDate>Mon, 02 Jun 2008 20:55:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209256#M32725</guid>
      <dc:creator>romano r</dc:creator>
      <dc:date>2008-06-02T20:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209257#M32726</link>
      <description>&lt;!--!*#--&gt;It should work at least for local, for example:&lt;BR /&gt;&lt;BR /&gt;# ls -la /home/ferreiri/.bashrc&lt;BR /&gt;-rw-r--r--  1 ferreiri ferreiri 124 jun 18  2007 /home/ferreiri/.bashrc&lt;BR /&gt;&lt;BR /&gt;# cp /home/ferreiri/.bashrc /tmp/prueba&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# ls -la /tmp/prueba&lt;BR /&gt;-rw-r--r--  1 root root 124 jun  2 18:29 /tmp/prueba&lt;BR /&gt;&lt;BR /&gt;# cp -p /home/ferreiri/.bashrc /tmp/prueba&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# ls -la /tmp/prueba&lt;BR /&gt;-rw-r--r--  1 ferreiri ferreiri 124 jun 18  2007 /tmp/prueba&lt;BR /&gt;&lt;BR /&gt;Can you post the same test done at your system?&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Jun 2008 21:30:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209257#M32726</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-06-02T21:30:16Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209258#M32727</link>
      <description>&amp;gt; [...] a standard user [...]&lt;BR /&gt;&lt;BR /&gt;&amp;gt; # cp -p [...]&lt;BR /&gt;&lt;BR /&gt;As I understand it, a _standard_ user is not&lt;BR /&gt;normally allowed to create files owned by&lt;BR /&gt;some other user.  Allowing this would tend to&lt;BR /&gt;make a joke out of disk quotas.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Can you post the same test done at your&lt;BR /&gt;&amp;gt; system?&lt;BR /&gt;&lt;BR /&gt;Or the actual commands you used and their&lt;BR /&gt;results.  Actual evidence (of the impossible)&lt;BR /&gt;is more convincing than vague descriptions.</description>
      <pubDate>Mon, 02 Jun 2008 21:50:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209258#M32727</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-06-02T21:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209259#M32728</link>
      <description>hello!&lt;BR /&gt;here the results:&lt;BR /&gt;user: pino&lt;BR /&gt;-rw-rw-r-- 1 romano users 69 2008-06-02 23:10 rocco&lt;BR /&gt;&lt;BR /&gt;&amp;gt; cp -p rocco ../pino/&lt;BR /&gt;&amp;gt; ll ../pino/&lt;BR /&gt;-rw-rw-r-- 1 pino users 69 2008-06-02 23:10 rocco&lt;BR /&gt;&lt;BR /&gt;thnk you</description>
      <pubDate>Mon, 02 Jun 2008 22:32:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209259#M32728</guid>
      <dc:creator>romano r</dc:creator>
      <dc:date>2008-06-02T22:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209260#M32729</link>
      <description>disk quota not enabled</description>
      <pubDate>Mon, 02 Jun 2008 22:33:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209260#M32729</guid>
      <dc:creator>romano r</dc:creator>
      <dc:date>2008-06-02T22:33:43Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209261#M32730</link>
      <description>&amp;gt; disk quota not enabled&lt;BR /&gt;&lt;BR /&gt;That does not make it a good idea to let "a&lt;BR /&gt;standard user" create files which some other&lt;BR /&gt;user owns.  It's only one of the reasons, not&lt;BR /&gt;the only reason.  For another example,&lt;BR /&gt;consider a file with rw-r--r-- permissions.&lt;BR /&gt;After you create it, if someone else owns it,&lt;BR /&gt;how do you delete it?  You don't have&lt;BR /&gt;permission to delete it, and you don't have&lt;BR /&gt;permission to change its permissions.&lt;BR /&gt;Allowing this would not be wise.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; here the results:&lt;BR /&gt;&lt;BR /&gt;I want to see where this works "ok" on an&lt;BR /&gt;"HP-UX 11i" system.  (And what, exactly, is&lt;BR /&gt;"HP-UX 11i"?  Show "uname -a" output.)</description>
      <pubDate>Tue, 03 Jun 2008 01:33:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209261#M32730</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-06-03T01:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209262#M32731</link>
      <description>This feature is sometimes called "allow file giveaway". It was an old Unix feature which has been found to be a security risk.&lt;BR /&gt;&lt;BR /&gt;In Linux, it's generally disabled by design. If you use a XFS filesystem, you can enable it by setting /proc/sys/fs/xfs/restrict_chown to 0. The default value is 1. Other filesystem types don't seem to allow this feature at all.&lt;BR /&gt;&lt;BR /&gt;In HP-UX, it's a system-wide feature controlled by setprivgrp() or the /etc/privgrp file.&lt;BR /&gt;&lt;BR /&gt;If the /etc/privgrp file contains the string "-g CHOWN" when the system boots, anyone is allowed to change the ownerships of files. I think this used to be the default on some *old* HP-UX default installations.&lt;BR /&gt;&lt;BR /&gt;If a HP-UX security auditor is worth his salt, he/she will certainly check this setting and ask for justification if it's enabled.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 03 Jun 2008 05:30:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209262#M32731</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-06-03T05:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209263#M32732</link>
      <description>on hp-ux&amp;gt;&lt;BR /&gt; uname -a&lt;BR /&gt;HP-UX lochp10 B.11.11 U 9000/800 1560605287 unlimited-user license&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Jun 2008 05:33:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209263#M32732</guid>
      <dc:creator>romano r</dc:creator>
      <dc:date>2008-06-03T05:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: allow cp -p to keep owner</title>
      <link>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209264#M32733</link>
      <description>"man chown" suggests "man 1m setprivgrp", too.</description>
      <pubDate>Tue, 03 Jun 2008 06:34:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/allow-cp-p-to-keep-owner/m-p/4209264#M32733</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-06-03T06:34:08Z</dc:date>
    </item>
  </channel>
</rss>

