<?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: why 4755? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869328#M98015</link>
    <description>4755 is different from 755&lt;BR /&gt;&lt;BR /&gt;4755 is providing the setgid permissions i.e.&lt;BR /&gt;rwx-r-sr-x in the file.&lt;BR /&gt;&lt;BR /&gt;When setgid permission is set on an executable file, a&lt;BR /&gt;process that runs this file is granted access based on the group of the file rather than the user who is running the executable file.&lt;BR /&gt;&lt;BR /&gt;This allows a user to&lt;BR /&gt;access files and directories that are normally only available to the owner/group. &lt;BR /&gt;&lt;BR /&gt;for example consider the mail command &lt;BR /&gt;/usr/bin/mail&lt;BR /&gt;&lt;BR /&gt;-r-sr-sr-x   2 root       mail         45056 Nov  7  1997 /usr/bin/mail &lt;BR /&gt;Here the owner and group are root and mail.&lt;BR /&gt;&lt;BR /&gt;Having setgid on this executable makes the normal users to obtain the group privileges(mail group) during the execution of this command// only during the execution//&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Mon, 23 Dec 2002 10:13:36 GMT</pubDate>
    <dc:creator>T G Manikandan</dc:creator>
    <dc:date>2002-12-23T10:13:36Z</dc:date>
    <item>
      <title>why 4755?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869327#M98014</link>
      <description>Hello, Rajvee,&lt;BR /&gt;&lt;BR /&gt;  I have a question here. Why do we have to set the permission with 4755 instead of 755?&lt;BR /&gt;&lt;BR /&gt;  Thanks a lot!</description>
      <pubDate>Mon, 23 Dec 2002 09:57:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869327#M98014</guid>
      <dc:creator>Lalo_Weng</dc:creator>
      <dc:date>2002-12-23T09:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: why 4755?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869328#M98015</link>
      <description>4755 is different from 755&lt;BR /&gt;&lt;BR /&gt;4755 is providing the setgid permissions i.e.&lt;BR /&gt;rwx-r-sr-x in the file.&lt;BR /&gt;&lt;BR /&gt;When setgid permission is set on an executable file, a&lt;BR /&gt;process that runs this file is granted access based on the group of the file rather than the user who is running the executable file.&lt;BR /&gt;&lt;BR /&gt;This allows a user to&lt;BR /&gt;access files and directories that are normally only available to the owner/group. &lt;BR /&gt;&lt;BR /&gt;for example consider the mail command &lt;BR /&gt;/usr/bin/mail&lt;BR /&gt;&lt;BR /&gt;-r-sr-sr-x   2 root       mail         45056 Nov  7  1997 /usr/bin/mail &lt;BR /&gt;Here the owner and group are root and mail.&lt;BR /&gt;&lt;BR /&gt;Having setgid on this executable makes the normal users to obtain the group privileges(mail group) during the execution of this command// only during the execution//&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 23 Dec 2002 10:13:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869328#M98015</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-23T10:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: why 4755?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869329#M98016</link>
      <description>Minor, but important, nit:&lt;BR /&gt;&lt;BR /&gt;4XXX is set *user* ID.&lt;BR /&gt;&lt;BR /&gt;[2XXX is set group ID. 6XXX is set user and group ID.]&lt;BR /&gt;&lt;BR /&gt;For details see the chmod(1) manual page.</description>
      <pubDate>Mon, 23 Dec 2002 13:18:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869329#M98016</guid>
      <dc:creator>Frank Slootweg</dc:creator>
      <dc:date>2002-12-23T13:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: why 4755?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869330#M98017</link>
      <description>I have completely messed up.&lt;BR /&gt;Yes,&lt;BR /&gt;4 is setuid&lt;BR /&gt;2 is setgid&lt;BR /&gt;&lt;BR /&gt;4755 is enabling setuid permissions.&lt;BR /&gt;&lt;BR /&gt;THe same process applies to setuid.&lt;BR /&gt;WHen you assign setuid for the file then the user executing it will be allowed for the privileges of the owner during the time of execution.Like the /usr/bin/passwd command.&lt;BR /&gt;Even though the normal users do not have privileges to edit the /etc/passwd file but by using /usr/bin/passwd they can change the password.&lt;BR /&gt;So setuid is enabled on the /usr/bin/passwd executable so that the roor privileges are got during the time of execution of the passwd command thus changing password and updating the password file.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 23 Dec 2002 13:24:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/why-4755/m-p/2869330#M98017</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-23T13:24:34Z</dc:date>
    </item>
  </channel>
</rss>

