3 ms·
> That package was just something you googled that hasn't been updated in two years because maven has required signed packages forever. That something hasn't b
by veeti 9y ago
> That package was just something you googled that hasn't been updated in two years because maven has required signed packages forever.
That something hasn't been updated in two years because it's feature complete and does what it's supposed to: verifies the integrity of dependencies for Signal [1].
> If someone gains access to my account and tries to modify my package without my private key it will not be accepted into the repo.
This isn't true. Sonatype/Maven Central requires PGP signatures on all new artifacts, but there is no requirement to use the same key. It will happily accept a signature from _any_ key for new releases.
[1] https://github.com/WhisperSystems/Signal-Android/blob/ae93038d6651b564f4957ecdcab7323346153bf2/build.gradle#L122 https://github.com/WhisperSystems/Signal-Android/blob/ae9303...
- ulldma 9y agoYes, this is important: Maven Central/Sonatype only checks if the submitted artifacts are signed (regardless of the used key). The work is shifted to client, but there's currently no standardized way on how to verify dependencies and plugins. There's an issue in the Maven bug tracker with the idea to extend the POM to allow trust information: https://issues.apache.org/jira/browse/MNG-6026 https://issues.apache.org/jira/browse/MNG-6026