Atomic Basic ModSecurity rule-set cannot be enabled: Invalid GPG Key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt: No key found in given key data

Symptoms

• Atomic Basic ModSecurity rule-set cannot be enabled at Tools & Settings > Web Application Firewall (ModSecurity) with the following error:

  PLESK_ERROR: ModSecurity failed to install rule set. modsecurity_ctl failed: gpg:
  key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg:
  Total number processed: 1 gpg: unchanged: 1 gpg:
  Signature made Sat Aug 26 00:11:22 2017 JST using RSA key ID 4520AFA9 gpg:
  Good signature from "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" gpg:
  
  WARNING: This key is not certified with a trusted signature! gpg:
  There is no indication that the signature belongs to the owner.
  Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set.
  warning: rpmts_HdrFromFdno: Header V4 RSA/SHA256 Signature, key ID 4520afa9:
  
  NOKEY Invalid GPG Key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt:
  No key found in given key data
  Command '/bin/bash < /tmp/tmpFHsuEp/aum' returned non-zero exit status 1
  Unable to download tortix rule set

• The GPG key mentioned in the error message is invalid or empty:

  # cat /etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt
  #

Cause

Invalid GPG key.

Resolution

1. Connect to a Plesk server via SSH.

2. Download a valid GPG key from the official Atomicorp website:

   # wget -P /root https://www.atomicorp.com/RPM-GPG-KEY.atomicorp.txt

3. Remove the invalid GPG key:

   # rm -f /etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt

4. Move the new GPG key to the corresponding directory:

   # mv /root/RPM-GPG-KEY.atomicorp.txt /etc/pki/rpm-gpg/RPM-GPG-KEY.atomicorp.txt

5. Restart Plesk services:

   # service sw-cp-server restart && service sw-engine restart

6. Enable Atomic Basic ModSecurity rule-set in Plesk.