Bug 31598

Summary:	The keyserver used by Mageiasync is no longer available
Product:	Mageia	Reporter:	Thomas Andrews <andrewsfarm>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, sysadmin-bugs, yvesbrungard
Version:	8	Keywords:	advisory, validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA8-64-OK
Source RPM:		CVE:
Status comment:

Description Thomas Andrews 2023-02-26 02:35:56 CET

Description of problem:
The keyserver currently used by Mageiasync is no longer available. Mageiasync needs to be changed to use a different one.

See bug 29895 comment 16 for more information.

Comment 1 papoteur 2023-02-26 08:38:33 CET

The version 0.4.4 is coming. The url of the server is changed to keyserver.ubuntu.com

packages:
mageiasync-0.4.4-1.mga8.noarch.rpm
Sources:
mageiasync-0.4.4-1.mga8.src.rpm

Assignee: bugsquad => qa-bugs
CC: (none) => yves.brungard_mageia

Comment 2 Dave Hodgins 2023-02-26 19:18:40 CET

Tested by creating a new user, copying just an iso file to it's home directory,
then running mageiasync to copy the checksum and sig files. After it fails
the sha3 check (due to the lack of use of detached signatures) ...
[tester@x3 ~]$ gpg --list-keys
/home/tester/.gnupg/pubring.kbx
-------------------------------
pub   rsa4096 2012-04-18 [SCEA] [expires: 2024-02-04]
      B21076A0CBE4D93D66A9D08D835E41F4EDCA7A90
uid           [ unknown] Mageia Release <release@mageia.org>

Confirmed it correctly imported the key for that user.

Validating the update. Advisory committed to svn.

Keywords: (none) => advisory, validated_update
Whiteboard: (none) => MGA8-64-OK
CC: (none) => davidwhodgins, sysadmin-bugs

Comment 3 Mageia Robot 2023-02-27 21:28:44 CET

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2023-0020.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED