You are not logged in.
While trying to install the "john 1.7.9-7" package, I get the message
kestrel:/home.kestrel/raymond# pacman -S john
resolving dependencies...
looking for inter-conflicts...
Packages (1): john-1.7.9-7
Total Download Size: 1.04 MiB
Total Installed Size: 3.40 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
john-1.7.9-7-x86_64 1061.4 KiB 1643K/s 00:01 [######################] 100%
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
error: john: signature from "Thorsten Tpper <atsutane@freethoughts.de>" is unknown trust
:: File /var/cache/pacman/pkg/john-1.7.9-7-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] I got this on two different computers on which "pacman -Syy" had been run recently. Since john tries to crack passwords, I am especially hesitant to use it when it is flagged as corrupted. Does it simply need to be redone with the updated arch keyring in place? Do I need to do something on my own computers to fix this?
Last edited by djraymondnm (2014-03-04 16:29:40)
Offline
Edit: First make sure your system is up to date as alphaniner suggests in the next post.
You might want to try and execute "pacman-key --refresh-keys" and "--updatedb" as root to refresh the keys after they have changed.
https://wiki.archlinux.org/index.php/Pa … ion_failed
You might want to try and execute "pacman-key --refresh-keys" and "--updatedb" as root to refresh the keys after they have changed.
https://wiki.archlinux.org/index.php/Pa … ion_failed
Last edited by progandy (2014-03-04 15:34:54)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Do you mean pacman -Syu has been run recently? Syy just force-updates your package databases, and installing new software on an un-updated system is not supported.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Thanks!
The key update commands
You might want to try and execute "pacman-key --refresh-keys" and "--updatedb" as root to refresh the keys after they have changed.
worked. Not doing pacman -Suy wasn't the issue in this particular case, as this had been done recently.
Offline