[slf4j-user] Signatures for verifying Slf4j

[Jeff Jensen]

It is best if the artifacts are signed.  Sometime in the near future,
Central/Nexus will not accept artifacts without being signed.

 

This would prove the source for you more than the hashes.

 

Ceki: you should start signing the release artifacts.  It is very easy -
I've done it already on a few products and Sonatype has a very good page
describing how.  Maven will do it automatically for you:

http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-m
aven

 

 

 

From: slf4j-user-bounces at qos.ch [mailto:slf4j-user-bounces at qos.ch] On Behalf
Of Joern Huxhorn
Sent: Friday, May 07, 2010 3:50 AM
To: User list for the slf4j project
Subject: Re: [slf4j-user] Signatures for verifying Slf4j

 

One solution could be the use of signed tags for SLF4J and Logback.

 

That way it would be possible to pull the git repository, check the
signature of the tag and build SLF4J and Logback yourself afterwards.

I think the MD5 and SHA1 of Maven repository are merely a way to prevent
corrupted files, not an actual security feature.

 

Cheers,

Joern.

 

On 07.05.2010, at 09:26, Elisha Ebenezer wrote:





Hi Ceki,
I'm trying to push to use Slf4j and logback in our project and my company
wants me to get the MD5 or SHA1 hashes or the code-signing certs to verify
the integrity of downloaded files.
 
Though repo1.maven.org <http://repo1.maven.org/>  site provides the hashes,
we are not sure whether the war and the hash are uploaded by genuine party
or not.
 
As you are the owner of the project, I request you to kindly publish the
hashes or certs on website's download page.. which can be cross-checked with
the downloaded war and/or also with the maven repository.
 
Kindly do the needful and oblige.
 
Thanks,
Elisha Ebenezer. _______________________________________________
slf4j-user mailing list
slf4j-user at qos.ch
http://qos.ch/mailman/listinfo/slf4j-user

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://qos.ch/pipermail/slf4j-user/attachments/20100507/911c8c9e/attachment-0001.html>