Project

General

Profile

Privacy issue #2275

Issues about PGP key Erich Eckner

pisechka - over 1 year ago - . Updated 3 months ago.

Status:
not-a-bug
Priority:
bug
Assignee:
-
% Done:

0%


Description

Hello.Recently I have migrated from ArchLinux on Parabola and got difficulties with upgrading keys. Pacman told me that it is wrong PGP key archlinux32-keyring and some troubles with archlinuxarm-keyring. So I had to run 1.1.1 from this guide [[https://wiki.parabola.nu/Pacman_troubleshooting]]. And recently downloaded Parabola 2019.03.10 and run it in virtual machine, got some problems. Now I have that keys and sigs by arch@eckner (pined file).
Tell me is it secure and correct? Sorry if my issue is stupid and not correct.


Files

keys_and_sigs_erich_eckner (2.32 KB) keys_and_sigs_erich_eckner pisechka, 2019-04-09 12:12 PM
Screenshot_2019-04-06_16-49-35.png (26.5 KB) Screenshot_2019-04-06_16-49-35.png pisechka, 2019-04-23 05:20 AM

History

#1

Updated by bill-auger over 1 year ago

this is what i have in my keyring

# pacman-key --list-keys arch@eckner.net
pub   rsa4096 2016-04-13 [SC] [revoked: 2018-04-11]
      7C98C4C3DE926168DC46FBAA3D06644243BF68D3
uid           [ revoked] Erich Eckner (just to sign arch packages) <arch@eckner.net>

pub   rsa4096 2018-04-09 [SC] [expires: 2020-04-08]
      5FDCA472AB93292BC678FD59255A76DB9A12601A
uid           [  full  ] Erich Eckner (just to sign arch packages) <arch@eckner.net>
sub   rsa4096 2018-04-09 [S] [expires: 2020-04-08]

im a bit confused about what you did or why - the instructions you linked to only specify to install the 'archlinux-keyring' and 'parabola-keyring' packages - erch's key is in the 'archlinux32-keyring', so those instructions should not have changed his key

in any case, the keyrings need updating routinely - this is a common event - all that you normally should need to do is update the package like any other

# pacman -Sy archlinux32-keyring

are you running a 32-bit i686 system?

did the migration guide not mention to install the 'archlinux32-keyring' package also?

were you just asking for someone to confirm that key?

are you having any problem with the system?

#2

Updated by bill-auger over 1 year ago

  • Status changed from unconfirmed to info needed
#3

Updated by pisechka over 1 year ago

I have the same key.

I use the x86_64 system, but during the migration and execution of # pacman -Suu pacman your-freedom the package manager demanded to update the archlinux32-keyring and don't confirmed the key.

I'm wondering why the same problems occur when running an image, you can try it yourself.

The system works correctly except broken dependencies icu ver.64 but I'm just wait fix it. I just care about my safety.

Sorry for my language and message form.

#4

Updated by bill-auger over 1 year ago

what exactly is the problem when running an image?

rather than explaining with words, it is always much more helpful if you show here some exact commands that you type and the error outputs that you see

#5

Updated by pisechka over 1 year ago

Just execute "# pacman -Syu" on fresh image and error.

#6

Updated by bill-auger 3 months ago

  • Status changed from info needed to not-a-bug

Also available in: Atom PDF