Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.4.4
-
Component/s: Packaging
-
Labels:None
-
Environment:RHEL and other RPM-based distros
-
Sprint:MXS-SPRINT-97, MXS-SPRINT-98, MXS-SPRINT-99, MXS-SPRINT-100, MXS-SPRINT-113
Description
MaxScale RPMs are signed by a key belonging to maxscale@googlegroups.com. This may be a problem for the environments with strict rules for key management. Auditors may ask why a supported product is signed by a key that does not belong to the vendor.
It makes sense to renew the key with an @mariadb.com one or release "Enterprise" MaxScale RPMs signed by one.