Closed Kortanul closed 3 years ago
Issue filed with pgpverify: https://github.com/s4u/pgpverify-maven-plugin/issues/24
we may be able to fix it in our fork of it.
as of 2.2.0, this issue should now be resolved -- we're now putting the PGP whitelist in a Maven artifact that should be proxy-friendly.
Per comment from @siepkes in https://github.com/WrenSecurity/wrends/pull/24, this is still an issue for the GPG signature requests. Re-opening.
I believe we can provide a documented workaround for this issue. Ideally we'd pull the HTTP proxy from Maven, but I remember this not being straightforward.
This should be fixed in upstream - https://www.simplify4u.org/pgpverify-maven-plugin/check-mojo.html#proxyName and we are already using the latest version of the plugin.
Summary
pgpverify-maven-plugin
is unable to retrieve the Wren trusted keys list when the local machine is behind a proxy, even when Maven is configured to use the proxy.Steps
wrensec-parent
) on a machine that's behind a proxy.~/.m2/settings.xml
).mvn clean install
in the root of the checked-out project.Expected
Project builds without issue.
Current
Build fails with a failure to resolve
wrensecurity.org
:Workarounds
mvn -Dignore-artifact-sigs clean install
works, but that completely skips PGP verification of artifacts (less secure).