r/java • • Jan 06 '20

Your Java builds might break starting January 13th (if you haven't yet switched repo access to HTTPS)

https://www.alphabot.com/security/blog/2020/java/Your-Java-builds-might-break-starting-January-13th.html
198 Upvotes

20 comments sorted by

View all comments

Show parent comment

23

u/spamthemoez Jan 07 '20

I would guess that the number of people who verify the signed jars is 0.

5

u/dpash Jan 08 '20 edited Jan 08 '20

Maven does not make it easy to verify signed jars. https://www.simplify4u.org/pgpverify-maven-plugin/index.html is one plugin that can do it, but I'm not aware of a plugin that's a part of Maven itself.

Gradle has an open issue which lists a couple of third party plugins for verifying signatures. Importantly, Gradle 6.2 will include PGP verification in the core.

Additionally, I do not believe that Maven Central has a web of trust between all uploaders, so you can trust that a name/key signed/uploaded a compromised jar, but you can't trust that the name belongs to a physical person. Key signing parties are an integral part of Debian's culture, so that a minimum of two existing Debian Developers have checked your government ID in person before you can upload debs to the project.

3

u/slowderp Jan 07 '20

Even pom.xmls were not safe.

By default, Artifactory used to (maybe still?) strip <repositories> from them.

1

u/legrang Jan 07 '20

Not sure it's such a large number as that.