I suppose that repo.opengeo.org has a broken checksum value:
federico@CIO311:~$ wget -c
http://repo.opengeo.org/org/beanshell/bsh/2.1b5/bsh-2.1b5.pom
--2012-05-28 15:47:56--
http://repo.opengeo.org/org/beanshell/bsh/2.1b5/bsh-2.1b5.pom
Risoluzione di repo.opengeo.org (repo.opengeo.org)... 173.236.65.86
Connessione a repo.opengeo.org (repo.opengeo.org)|173.236.65.86|:80...
connesso.
Richiesta HTTP inviata, in attesa di risposta... 200 OK
Lunghezza: 460 [text/plain]
Salvataggio in: "bsh-2.1b5.pom"
100%[======================================>] 460 --.-K/s in 0s
2012-05-28 15:47:56 (27,9 MB/s) - "bsh-2.1b5.pom" salvato [460/460]
federico@CIO311:~$ md5sum bsh-2.1b5.pom
5a9277846d9eb92a5607cb70e2b23db2 bsh-2.1b5.pom
So, the best checksum policy in this case is?
(3) Ignore and generate: Artifactory will locally generate a checksum for
both bad or
missing remote checksum. Remote resource retrieval will never fail, but
integrity might
be compromised.
OR
(4) Pass-thru: Artifactory will store and pass-thorugh all remote checksums
including
bad ones and will locally generate a checksum for a missing remote checksum
cannot be
found. Remote resource retrieval will never fail, but integrity might be
compromised and
client-side checksum validation (such as the one done by Maven) will fail.
Thank you
Federico
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
