How can I force `rpm` and `yum` to fail if a GPG signature is missing from a package or otherwise cannot be verified due to a missing key? For the example below, assume the RPM has been signed but the key has not been installed.

With RPM I see a warning, but I would like this to fail so that I am forced to manually install the signing key.

```
# rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n'
gpg-pubkey-c105b9de-4e0fd3a3 --> gpg(CentOS-6 Key (CentOS 6 Official Signing Key) <centos-6-key@centos.org>)

# rpm -ivh http://yum.example.com/company-release-el-6.noarch.rpm
Retrieving http://yum.example.com/company-release-el-6.noarch.rpm
warning: /var/tmp/rpm-tmp.3VmFk2: Header V4 RSA/SHA1 Signature, key ID 3bd6ec30: NOKEY
Preparing...                ########################################### [100%]
    1:company-release     ########################################### [100%]

```

With yum, I see no warnings related to the fact that the signing key is not installed.

```
# yum install -vy http://yum.example.com/company-release-el-6.noarch.rpm

```

Are there additional flags I can pass to these commands or a configuration setting I can modify to change the behavior? Or must I download the RPM and run `rpm --checksig` prior to installation?