umask settings

[andyrsharma]

Hi All,
I am a newbie to documentum and to this forum. In my organization, we are using documentum 5.3 on solaris. We have world writable files (public files) created by documentum

dir.lck files and directories in share/data/common

I have so far tried to add umask=2 in dmcl.ini, server.ini and docbroker startup script.
Unfortunately, non of these methods have so far not helped in generation of these folders/files.



Any help will be greatly appreciated.


Thanks

[johnnygee_va]

What files underneath common are you trying to make public? Are you trying to write log files?

[andyrsharma]

these are directories which are world writable. rw-rw-rw
world writable/public updatable files are a security issue. By setting umask=2 (in unix) the writbale bit is turned off.

Documentum is creating these folders everyday and they all have these world writable bits turned on.
These folders resides at
/users/documentum/share/data/common/

What do I like to do?
By default, documentum generates rw-rw-rw files, how do I default it to rw-rw-r (writable bit off)?

I heard somewhere that by setting umask=2 in dmcl.ini and server.ini will solve this problem but unfortunately, it didnt worked for these folder (I think it did worked for other folders though)

[johnnygee_va]

Why should the world have access to these files? If this is your filestore for content repository, then only Documentum installation owner should have permissions on the physical files. All other users/applications should only access content via DFC/DFS methods. This ensures that the security model is followed. If you want everyone to access the content, then you should publish the content to a website.

[bonsky]

hi andyrsharma,

have you manage to figure out how to do this thing? I am facing the same issue here. tried server.ini and dmcl.ini as well . Also change the profile of the installation owner, but seems like not working for me.
do you have the solution?