Clovertech

umask properties changed when upgrading to v20.1

› Clovertech Forums › Cloverleaf › umask properties changed when upgrading to v20.1

  • Creator
    Topic
  • September 9, 2021 at 4:29 pm #119164
    Carl Tosi
    Participant

      We noticed that when we upgraded from v6.2 to v20.1 that the umask properties seemed to have changed.

      Currently in our TEST environment the umask is set to 0077. Previously it was set to 0002. We are trying to determine if the change was due to our upgrading to v20.1.
      Has anyone else encountered this problem ?

      Thanks,
      Carl Tosi

    • Creator
      Topic
    Viewing 1 reply thread
    • Author
      Replies
      • September 10, 2021 at 8:43 am #119165
        John Mercogliano
        Participant

          We just did a clean install of 20.1 on redhat.  We are migrating from 6.1 Aix.  But on the clean install the umask in the provided .profile when hci was created was 007.

          We have always added our own umask to the .profile.local.end

           

          John Mercogliano
          Sentara Healthcare
          Hampton Roads, VA

        • September 12, 2021 at 12:22 am #119168
          Charlie Bursell
          Participant

            It is the security measure that all need now a days.  A umask 0f 0002 would allow owner and group read/write and others read only (rw-rw-r) permissions.  The new one allows read/write only to the owner (rw–).

             

            As stated you can change to whatever you require.

        • Author
          Replies
        Viewing 1 reply thread
        • You must be logged in to reply to this topic.