Please sign 0xB46DE9BF9BE56E4BC565251E1C5FBD462034AEEE key with webmaster's one
Summary
Key 0xB46DE9BF9BE56E4BC565251E1C5FBD462034AEEE (Eclipse Exousia exousia-dev@eclipse.org) seems to have no webmaster's signature published.
Steps to reproduce
gpg --keyserver pgp.mit.edu --recv-key 0xB46DE9BF9BE56E4BC565251E1C5FBD462034AEEE
wget https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/exousia/exousia/2.1.0/exousia-2.1.0.jar
wget https://jakarta.oss.sonatype.org/content/repositories/staging/org/glassfish/exousia/exousia/2.1.0/exousia-2.1.0.jar.asc
gpg --verify exousia-2.1.0.jar.asc
What is the current bug behavior?
gpg: Good signature from "Eclipse Exousia <exousia-dev@eclipse.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
What is the expected correct behavior?
To have 0xB46DE9BF9BE56E4BC565251E1C5FBD462034AEEE signed by [trusted] webmaster (0x9FA2B7299F51E543).
Relevant logs and/or screenshots
Similar to: