QnaList > Groups > Play-Framework > Jan 2013
faq

[2.0.4] Play 2.0.4 Artifact Signature And Cross-build Injection Attacks

Hi there,
I was reading today on how RubyGems (the Ruby equivalent of Maven central) got a malicious gem uploaded due to a security vulnerability and how they're verifying the rest of the gems(more info at https://status.heroku.com/incidents/489).
It got me curious as to how this affects my play app, so using sbt-pgp 0.6, I ran check-pgp-signatures. It seems that the play 2.0.4 artifacts are unsigned:
[info] ----- PGP Signature Results -----
[info] � � � � � � � �com.google.apis : �google-api-services-oauth2 : v2-rev26-1.12.0-beta : jar � [MISSING]
[info] � � � � � � � � �commons-email : � � � � � � � commons-email : � � � � 1.2-SNAPSHOT : jar � [MISSING]
[info] � � � � � � � org.bouncycastle : � � � � � � �bcprov-jdk15on : � � � � � � � � 1.47 : jar � [MISSING]
[info] � � � � � � � � � � � � � play : � � � � � � play-test_2.9.1 : � � � � � � � �2.0.4 : jar � [MISSING]
[info] � � � � � � � � � � � � � play : � � � � � � � � �play_2.9.1 : � � � � � � � �2.0.4 : jar � [MISSING]
[info] � � � � �com.google.api-client : � � � � � google-api-client : � � � � �1.12.0-beta : jar � [UNTRUSTED(0x978e282a)]
[info] � � � � � � � com.google.guava : � � � � � � � � � � � guava : � � � � � � � � 11.0 : jar � [UNTRUSTED(0x4931a76)]
[info] � � � � com.google.http-client : google-http-client-jackson2 : � � � � �1.12.0-beta : jar � [UNTRUSTED(0x978e282a)]
[info] � com.google.inject.extensions : � � � � guice-multibindings : � � � � � � � � �3.0 : jar � [UNTRUSTED(0x102b84d)]
[info] � � � � � � �com.google.inject : � � � � � � � � � � � guice : � � � � � � � � �3.0 : jar � [UNTRUSTED(0x102b84d)]
...
Are there plans, in the future, to sign the play framework artifacts? Also, are there other developers checking their artifacts signatures, and if so, how do you do it and what do you think are the best practices in that regards?
Thanks in advance,
-JF

asked Jan 30 2013 at 15:06

Jean-François Im's gravatar image



1 Replies for : [2.0.4] Play 2.0.4 Artifact Signature And Cross-build Injection Attacks
Are there plans, in the future, to sign the play framework artifacts?
Yes, there are now plans to do this. �However, it requires some significant changes to our build process, since currently we actually build Play twice, once for publishing to the Typesafe ivy repository, and once for the zip distribution. �We could sign jars in the Typesafe repository today, but since the contents of the jars will be different (different timestamps of the class files in the jars), the signatures in the repository won't match the signatures of the jars in the zip distribution, and this would likely lead to false alarms saying the signature check failed if someone ran check-pgp-signatures.
So it will happen, but maybe not until 2.2.
�
Thanks in advance,
-JF
-- 
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
�
�
-- 
James Roper
Software Engineer
Typesafe�-�The software stack for applications that scale
Twitter: @jroper

answered Jan 30 2013 at 23:26

James Roper's gravatar image


Related discussions

Tagged

Group Play-framework

asked Jan 30 2013 at 15:06

active Jan 30 2013 at 23:26

posts:2

users:2

Play-framework

©2013 QnaList.com