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 15:05:25 -0500
Subject: secure dependency artifacts
Thread-Topic: secure dependency artifacts
Thread-Index: AcimRoiIY3dQX/XOQLexIDNP1lB9gg==
Message-ID: 
 <745B9EDF57802349B13F90E4E0B4B86C3BA402BB48@HOUEXCH012.corp.halliburton.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_745B9EDF57802349B13F90E4E0B4B86C3BA402BB48HOUEXCH012cor_"
MIME-Version: 1.0

--_000_745B9EDF57802349B13F90E4E0B4B86C3BA402BB48HOUEXCH012cor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Currently we have an ivy repository that is within our corporate firewall o=
n a shared Netapp storage device.  It is constantly being added to as each =
continuous build publishes its latest version.  In the past as part of the =
ANT build, we would zip up the source code used to produce each build and p=
ublish it as an artifact along with the build.  This is useful for when dev=
elopers working on modules high up in the dependency chain need to debug do=
wn to a dependent module inside their IDE.  Having the source zip files giv=
es them the source code to debug into.

This is working great, but here comes a new corporate policy.  We have to i=
ncrease 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 acces=
s to all source code.

So my question is if there is a way to have secured dependency artifacts?  =
Can we have all artifacts be readable but then have the source.zip require =
a username and password before it downloads with a resolve/retrieve?  Even =
if this were possible, we would still need to keep the shared netapp storag=
e device readable by everybody so that they could successfully download dep=
endencies other than the source zip files.

Any ideas?  Perhaps use the svnivy plugin and store our repository artifact=
s inside SVN which has authentication options to protect against what is ac=
cessible??

---
Shawn Castrianni

----------------------------------------------------------------------
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.
--_000_745B9EDF57802349B13F90E4E0B4B86C3BA402BB48HOUEXCH012cor_--