You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Benjamin Bentmann (JIRA)" <ji...@apache.org> on 2009/08/18 01:56:14 UTC
[jira] Created: (INFRA-2189) Please add setgid permission on
/www/maven.apache.org
Please add setgid permission on /www/maven.apache.org
-----------------------------------------------------
Key: INFRA-2189
URL: https://issues.apache.org/jira/browse/INFRA-2189
Project: Infrastructure
Issue Type: Wish
Security Level: public (Regular issues)
Components: Unix Groups
Reporter: Benjamin Bentmann
After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the *group* of the uploaded files gets set to the user performing the upload, see for instance the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware of a related change in our tooling and from some discussion on the Maven dev list I got the impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide the desired the effect, namely that newly created files automatically belong to the group "maven". The content in this directory is meant to be updated by all our committers, having the default group ownership for files being the user's primary group doesn't fit well in this context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2189) Please add setgid permission on
/www/maven.apache.org
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755810#action_12755810 ]
#asfinfra IRC Bot commented on INFRA-2189:
------------------------------------------
<brettporter> Tony has said this should be fixed now
> Please add setgid permission on /www/maven.apache.org
> -----------------------------------------------------
>
> Key: INFRA-2189
> URL: https://issues.apache.org/jira/browse/INFRA-2189
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Unix Groups
> Reporter: Benjamin Bentmann
>
> After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the *group* of the uploaded files gets set to the user performing the upload, see for instance the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware of a related change in our tooling and from some discussion on the Maven dev list I got the impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide the desired the effect, namely that newly created files automatically belong to the group "maven". The content in this directory is meant to be updated by all our committers, having the default group ownership for files being the user's primary group doesn't fit well in this context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2189) Please add setgid permission on
/www/maven.apache.org
Posted by "Benjamin Bentmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757725#action_12757725 ]
Benjamin Bentmann commented on INFRA-2189:
------------------------------------------
Seems fixed for the base directory but we actually need the flag set for all sub directories as well, i.e. something like
{noformat}
find . -type d \! -perm -g+s -exec chmod g+s {} \;
{noformat}
in {{/www/maven.apache.org}} should do I guess.
> Please add setgid permission on /www/maven.apache.org
> -----------------------------------------------------
>
> Key: INFRA-2189
> URL: https://issues.apache.org/jira/browse/INFRA-2189
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Unix Groups
> Reporter: Benjamin Bentmann
>
> After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the *group* of the uploaded files gets set to the user performing the upload, see for instance the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware of a related change in our tooling and from some discussion on the Maven dev list I got the impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide the desired the effect, namely that newly created files automatically belong to the group "maven". The content in this directory is meant to be updated by all our committers, having the default group ownership for files being the user's primary group doesn't fit well in this context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-2189) Please add setgid permission on
/www/maven.apache.org
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-2189.
------------------------------------
Resolution: Fixed
> Please add setgid permission on /www/maven.apache.org
> -----------------------------------------------------
>
> Key: INFRA-2189
> URL: https://issues.apache.org/jira/browse/INFRA-2189
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Unix Groups
> Reporter: Benjamin Bentmann
>
> After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the *group* of the uploaded files gets set to the user performing the upload, see for instance the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware of a related change in our tooling and from some discussion on the Maven dev list I got the impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide the desired the effect, namely that newly created files automatically belong to the group "maven". The content in this directory is meant to be updated by all our committers, having the default group ownership for files being the user's primary group doesn't fit well in this context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2189) Please add setgid permission on
/www/maven.apache.org
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757763#action_12757763 ]
#asfinfra IRC Bot commented on INFRA-2189:
------------------------------------------
<pquerna> Fixed recusrively, along with group ownerships.
> Please add setgid permission on /www/maven.apache.org
> -----------------------------------------------------
>
> Key: INFRA-2189
> URL: https://issues.apache.org/jira/browse/INFRA-2189
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Unix Groups
> Reporter: Benjamin Bentmann
>
> After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the *group* of the uploaded files gets set to the user performing the upload, see for instance the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware of a related change in our tooling and from some discussion on the Maven dev list I got the impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide the desired the effect, namely that newly created files automatically belong to the group "maven". The content in this directory is meant to be updated by all our committers, having the default group ownership for files being the user's primary group doesn't fit well in this context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.