[MXS-2804] MaxScale RPMs should be signed with key that belongs to @mariadb.com - Jira

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 2.4.4
Fix Version/s: 2.4.12, 2.5.3
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.

Attachments

Sub-Tasks

1.	Refactor Maxscale repository creation		Closed	Timofey Turenko
2.	Create several users on the repo signature server		Closed	Timofey Turenko

Activity

People

Assignee:: Timofey Turenko

Reporter:: Valerii Kravchuk

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2019-12-17 10:57

Updated:: 2024-07-07 17:01

Resolved:: 2020-08-27 10:36

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.