Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of
 Shawn.Castrianni@halliburton.com designates 34.254.16.16 as permitted sender)
From: Shawn Castrianni <Shawn.Castrianni@halliburton.com>
To: "'ivy-user@ant.apache.org'" <ivy-user@ant.apache.org>
Date: Thu, 24 Apr 2008 16:21:04 -0500
Subject: RE: secure dependency artifacts
Thread-Topic: secure dependency artifacts
Thread-Index: AcimSu/82kzO++QDTmeRIrcjEhWqIAABdChA
Message-ID: 
 <745B9EDF57802349B13F90E4E0B4B86C3BA402BB49@HOUEXCH012.corp.halliburton.com>
References: 
 <745B9EDF57802349B13F90E4E0B4B86C3BA402BB48@HOUEXCH012.corp.halliburton.com>
 <20080424203556.GA89242@nmhq.net>
In-Reply-To: <20080424203556.GA89242@nmhq.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

How would all the developers unencrypt it?  They each have their own creden=
tials with their own passwords.  What I am trying to achieve is for only th=
e developers that have access to the source code in the Subversion reposito=
ry to be able to see the src.zip when they do a resolve/retrieve.  That way=
 nobody is getting access to source code that they don't already have with =
Subversion.

---
Shawn Castrianni

-----Original Message-----
From: Niklas Matthies [mailto:ml_ivy-user@nmhq.net]
Sent: Thursday, April 24, 2008 3:36 PM
To: ivy-user@ant.apache.org
Subject: Re: secure dependency artifacts

On Thu 2008-04-24 at 15:05h, Shawn Castrianni wrote on ivy-user:
:
> This is working great, but here comes a new corporate policy.
> We have to increase the security of our source code and closely
> monitor who has access to what.  We do this with our SVN server, but
> by publishing the source.zip on a shared netapp storage device,
> anybody can go to the network share and browse into these source zip
> files. This essentially gives everybody access to all source code.

Why not just encrypt the source zip using something like PGP?
That would be both simplest and safest.

-- Niklas Matthies

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and pri=
vileged information for the sole use of the intended recipient.  Any review=
, use, distribution, or disclosure by others is strictly prohibited.  If yo=
u are not the intended recipient (or authorized to receive information for =
the intended recipient), please contact the sender by reply e-mail and dele=
te all copies of this message.