Permission on repository-folder

[Jørgen Staun Hansen]

After upgrade to 1.60 we noticed that when a repository is created some permissions are missing on the file-structure.

When creating a repository via web-interface or via script the permissions are like this.

drwx------   3 scm scm 4096 Jun  1 10:53 staun-test

Last week and earlier (before 1.60 we believe, we upgraded on monday 28th of may 2018) the missions were :

drwxr-xr-x  10 scm scm 4096 Apr 16 07:42 Test

After this change our SW-dev. cannot work with the repositories.

what should the permissions be and any idea what could cause this permission change?

[Sebastian Sdorra]

Hi,

SCM-Manager does not use any specific permissions, for the directories. SCM-Manager uses always the default settings. I think there is a miss configuraton in one of the parent directories on your server. 

You can check this on linux by using the getfacl command e.g.:

$ getfacl test 

# file: test

# owner: scm

# group: scm

user::rwx

group::r-x

other::r-x

default:user::rwx

default:group::rwx

default:other::r-x

The default entries are showing the permissions which are used for new directories.

But why would the "SW-dev" work directly with the directory? Why do not use the http interface of SCM-Manager?

Sebastian

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jørgen Staun Hansen]

Permissions for the parent-directory seems to be correct

root@srv-repo-nsb2:/home/repo/hg# getfacl Components

# file: Components

# owner: scm

# group: scm

user::rwx

group::r-x

other::r-x

But I wonder why this suddenly has changed since I upgraded this monday - The permissions er not "correct" even if we use the interface in SCM-Manager.

Our SW-dev. are using different command-line tools (HG etc.) which connects to the http://..../repo from their computers/ build-servers

To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.

[Jørgen Staun Hansen]

Ok, I have now restored all required servers to a test-enviroment, where SCM is running version 1.59

Then create a new repository from the GUI and check file-system permissions.

All things are good (Read and Execute on filesystem is good)

Upgrade SCM via Apt-get, create a new REPO and check filesystem permissions again.

XR (Read/ Execute) is now missing?? - what happend between version 1.59 and 1.60.

[Sebastian Sdorra]

I'm sorry, but i dont understand why 0700 permission are a problem at all. Because scm-manager should control every request to the repository. Or do you bypass scm-manager to access the repositories?

Sebastian

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+unsubscribe@googlegroups.com.

[Jørgen Staun Hansen]

We are using scripts running on the server that accesses the file-system directly (Read mode).

To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.

[Gerald Schneider]

I'm having the same issue. We are accessing the repositories directly from FishEye. I can understand the more restricted permissions from a security standpoint, but it would be nice if the permissions where at least 750, so we can control which applications can access the repositories via user groups.

Regards,

Gerald

To unsubscribe from this group and stop receiving emails from it, send an email to scmma...@googlegroups.com.