Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <1028444014.1205224966132.JavaMail.jira@brutus>
Date: Tue, 11 Mar 2008 01:42:46 -0700 (PDT)
From: =?utf-8?Q?Tero_Hagstr=C3=B6m_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVY-764) ssh resolver sets very restrictive file
 permissions when publishing artifacts
In-Reply-To: <759287683.1205149428768.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/IVY-764?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1257733=
6#action_12577336 ]=20

Tero Hagstr=C3=B6m commented on IVY-764:
-----------------------------------

Umask on both local and server is 0022.

I was playing around with Ivy 1.4.1 earlier, and managed to publish files o=
n the server so that their permissions were=20
rw-rw-r-, which is what I want.

I cannot reproduce that behaviour with ivy 1.4.1 anymore though. Now I get =
permissions rw------ with 1.4.1 too.=20

What affects the file permissions set for the published files?=20


> ssh resolver sets very restrictive file permissions when publishing artif=
acts
> -------------------------------------------------------------------------=
----
>
>                 Key: IVY-764
>                 URL: https://issues.apache.org/jira/browse/IVY-764
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0.0-beta-2
>            Reporter: Tero Hagstr=C3=B6m
>
> When we use the ssh resolver to publish artifacts to a repository on our =
server, the access permissions of the created files only allow reading by t=
he user that published the artifacts. As a result, no one else can get the =
artifacts from the repository, which completely defeats it's  purpose.
> File permissions look like this:
> -rw-------  1 atu dev 875 Mar 10 12:34 core-20080310123411.jar
> -rw-------  1 atu dev  40 Mar 10 12:34 core-20080310123411.jar.sha1
> -rw-------  1 atu dev  32 Mar 10 12:34 core-20080310123411.jar.md5
> -rw-------  1 atu dev 166 Mar 10 12:34 ivy-20080310123411.xml
> -rw-------  1 atu dev  40 Mar 10 12:34 ivy-20080310123411.xml.sha1
> -rw-------  1 atu dev  32 Mar 10 12:34 ivy-20080310123411.xml.md5
> I could not find any way to configure or otherwise affect the file permis=
sions. Is there a way?=20
> BTW, with Ivy 1.4.1 the permissions looked like this:
> -rw-rw-r--  1 th  dev 877 Mar  6 10:08 core-20080306100813.jar
> -rw-rw-r--  1 th  dev  40 Mar  6 10:08 core-20080306100813.jar.sha1
> -rw-rw-r--  1 th  dev  32 Mar  6 10:08 core-20080306100813.jar.md5
> -rw-rw-r--  1 th  dev 166 Mar  6 10:08 ivy-20080306100813.xml
> -rw-rw-r--  1 th  dev  40 Mar  6 10:08 ivy-20080306100813.xml.sha1
> -rw-rw-r--  1 th  dev  32 Mar  6 10:08 ivy-20080306100813.xml.md5
> We will now fall back to using Ivy version 1.4.1, for the time being.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.