Pacman-key local sign

Hi,
new installation, runned those commands:
pacman-key --init
pacman-key --populate archlinux
pacman-key --keyserver pgp.mit.edu --recv-keys 0xabed422d653c3094
pacman-key --lsign-key 0xabed422d653c3094
But the last command returns me
ERROR: The key identified by 0xabed422d653c3094 could not be found locally
Somebody got a clue ?
Thanks.

Yes my bad, didn't write what I am trying to do.
I'm trying to install this unofficial key, i posted the four commands to show that I didn't do some weird stuff before.
I initialised the keys with the two first commands, and then tried to install this unofficial key, which happend to fail, and I don't understand why.
Thanks for your reply ;-).

Similar Messages

[SOLVED] Can't sign key with pacman-key

I've been reading and digging all over the place but I can't seem to find anything on this.
1. I have created my own keys for signing packages that I want to put in a local repo so I don't have to compile the same package over and over on all my machines.
2. I have imported said key using sudo pacman-key --add rdjack21.pgp
3. Used sudo pacman-key --lsign rdjack21 I get this output:
-> Locally signing key rdjack21...
==> ERROR: rdjack21 could not be locally signed.
4. Ok so lets sudo pacman-key --edit rdjack21 output:
gpg> sign
pub rsa2048/3D1B5544
created: 2014-11-30 expires: never usage: SC
trust: ultimate validity: ultimate
Primary key fingerprint: B0D7 C728 31FA B2B0 6A3C 7086 DC7F DE0C 3D1B 5544
Richard Jackson <[email protected]>
Are you sure that you want to sign this key with your
key "Pacman Keyring Master Key <pacman@localhost>" (645ECB0E)
Really sign? (y/N) y
gpg: signing failed: No pinentry
gpg: signing failed: No pinentry
gpg>
5. To hack this and make pacman work with my local repo signed by the rdjack21 key I had to change the trust to ultimate but I do not like that solution. I would prefer to sign the key and move the trust back down to full which is where it should be.
This is happening on all of my boxes not just one of them. I did find something on the web about "No pinentry" message above and the sugestion was to change the owner of the tty I'm using to be root for the signing to work but that did not work for me (su'ed to root first instead of running everything with sudo).
While changeing the trust works that just feels wrong to me. I really should beable to sign the key.
Last edited by rdjack21 (2014-12-01 01:50:05)

Taking a clue post gnupg 2.1.0-4 upgrade breaks passphrase via STDIN I was able to solve the problem and I can now sign keys.
The solution is add "pinentry-mode loopback" to /etc/pacman.d/gnupg/gpg.conf
And create the file /etc/pacman.d/gnupg/gpg-agent.conf and put "allow-loopback-pinentry" in the file.
Once that is done everythings works as expected!
Marking this as solved.

[SOLVED] Pacman Key Signing Strange Activity

Hi,
I was just setting up the package verification system with pacman when I noticed it was doing something unusual. When I ran:
pacman-key --init
instead of waiting for entropy, it just returned the prompt. Next, when I ran:
pacman-key --populate archlinux
it seemed to go through the entire signing process itself, stating that they didn't need to be signed again (sorry for the vagueness as I can't fetch exactly what it said by redirecting it into a file or something). The point is, usually I have to confirm each signature.
Is this normal?
Last edited by Mindstormscreator (2012-08-26 15:42:40)

Does the contents of /etc/pacman.d/gnupg look normal? You could compare that directory with the one on the live media (diff -rq) to test that theory.
When I set up package signing, I think I signed five master keys manually which I'd compared from two somewhat independent sources. After that, I don't remember having to *sign* any more signatures but only to confirm it was OK to import them. And now pacman seems to handle much of that automatically... But it is hard to imagine it would be meant to sign the master keys automatically since that would seem to undermine the point of having them in the first place.
On a fresh install, too, the init should take longer because so little is going on. (Hence all the threads here about it hanging because people haven't read the instructions for creating entropy .)

[Solved] Using pacman's package signing correctly

When pacman 4 first came out, I just merged the pacnew file so that package signing was disabled. I did initialise the keys etc. but I didn't import or sign the master keys or enable signature checks.
So tonight I figured I would start seeing how this worked. I took the fingerprints from the master key list on archlinux's site and I checked they matched the fingerprints listed on Allan's blog. I then imported the five master keys using pacman-key, signed them locally and used --edit-key to assign each of the five marginal trust.
I then commented out the "Never" line for package signing in pacman.conf so that it would use the compiled in default to make signatures optional but check them if available. I also set PackageRequired for the core repository. I left the other repos I have enabled to default to the default policy as I think signing isn't complete for them.
I then ran pacman -Syu. This mostly went OK but I'm slightly worried about this bit:
error: gsm: key "7F2D434B9741E8AC" is unknown
:: Import PGP key 9741E8AC, "Pierre Schmitz <[email protected]>", created 2011-04-10? [Y/n] y
error: jbig2dec: key "BBE43771487328A9" is unknown
:: Import PGP key 487328A9, "Bartlomiej Piotrowski <[email protected]>", created 2011-10-10? [Y/n] y
error: p11-kit: key "E8F18BA1615137BC" is unknown
:: Import PGP key 615137BC, "Ionut Biru <[email protected]>", created 2011-04-19? [Y/n] y
error: pacmatic: key "396E3E25BAB142C1" is unknown
:: Import PGP key BAB142C1, "Kyle Keen <[email protected]>", created 2011-02-03? [Y/n] y
error: patchutils: key "06096A6AD1CEDDAC" is unknown
:: Import PGP key D1CEDDAC, "Laurent Carlier <[email protected]>", created 2011-10-30? [Y/n] y
error: perl-encode-locale: key "F99FFE0FEAE999BD" is unknown
:: Import PGP key EAE999BD, "Allan McRae <[email protected]>", created 2011-06-03? [Y/n] y
error: vlc: key "B7310AE5F04569AE" is unknown
:: Import PGP key F04569AE, "Giovanni Scafora <[email protected]>", created 2011-10-15? [Y/n] y
I initially thought I was just telling pacman to import the keys but now I'm wondering if I also told it to trust them and if I wasn't meant to do that? Should they have been automatically handled if they were signed correctly? I was trying to follow the instructions on Allan's blog which show this question and Allan answering yes. However, I now realise that I got confused and that that bit comes *before* Allan imports and trusts the master keys, but I'd already done that at this point. (But it didn't complain they were untrusted once imported...)
Could somebody either reassure me that I did this correctly (securely)? Or advise me on how to undo it if that's what I should do?
Last edited by cfr (2012-02-19 15:14:02)

I followed Allan's guide on page
http://allanmcrae.com/2011/12/pacman-pa … rch-linux/
and pacman -Syu gave:
error: xorg-bdftopcf: signature from "Allan McRae <[email protected]>" is marginal trust
Which is suprising as his key is one of master keys. Currently several master keys were revoked.
Based on GPG's output it is maybe requires some additional input to mark the revoked key as trusted:
sub 3072R/B20030F3 created: 2011-11-25 revoked: 2011-11-25 usage: A
[ full ] (1). Ionut Biru (Arch Linux Master Key) <[email protected]>
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
gpg gives this:
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
full story:
[root@archbang ~]# for key in FFF979E7 CDFD6BB0 4C7EA887 6AC6A4C2 824B18E8; do
> printf 'trust\n3\nquit\n' | gpg --homedir /etc/pacman.d/gnupg/ --no-permission-warning --command-fd 0 --edit-key $key
> done
pub 3072R/4C7EA887 created: 2011-11-25 expires: never usage: SC
trust: marginal validity: full
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 1024R/93F91AC3 created: 2011-11-25 revoked: 2011-11-25 usage: E
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 3072R/B20030F3 created: 2011-11-25 revoked: 2011-11-25 usage: A
[ full ] (1). Ionut Biru (Arch Linux Master Key) <[email protected]>
pub 3072R/4C7EA887 created: 2011-11-25 expires: never usage: SC
trust: marginal validity: full
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 1024R/93F91AC3 created: 2011-11-25 revoked: 2011-11-25 usage: E
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 3072R/B20030F3 created: 2011-11-25 revoked: 2011-11-25 usage: A
[ full ] (1). Ionut Biru (Arch Linux Master Key) <[email protected]>
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
pub 3072R/4C7EA887 created: 2011-11-25 expires: never usage: SC
trust: marginal validity: full
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 1024R/93F91AC3 created: 2011-11-25 revoked: 2011-11-25 usage: E
This key was revoked on 2011-11-25 by RSA key 4C7EA887 Ionut Biru (Arch Linux Master Key) <[email protected]>
sub 3072R/B20030F3 created: 2011-11-25 revoked: 2011-11-25 usage: A
[ full ] (1). Ionut Biru (Arch Linux Master Key) <[email protected]>
pub 3072R/6AC6A4C2 created: 2011-11-18 expires: never usage: SC
trust: marginal validity: full
sub 1024R/86872C2F created: 2011-11-18 expires: never usage: E
sub 3072R/1B516B59 created: 2011-11-18 expires: never usage: A
[ full ] (1). Pierre Schmitz (Arch Linux Master Key) <[email protected]>
pub 3072R/6AC6A4C2 created: 2011-11-18 expires: never usage: SC
trust: marginal validity: full
sub 1024R/86872C2F created: 2011-11-18 expires: never usage: E
sub 3072R/1B516B59 created: 2011-11-18 expires: never usage: A
[ full ] (1). Pierre Schmitz (Arch Linux Master Key) <[email protected]>
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
pub 3072R/6AC6A4C2 created: 2011-11-18 expires: never usage: SC
trust: marginal validity: full
sub 1024R/86872C2F created: 2011-11-18 expires: never usage: E
sub 3072R/1B516B59 created: 2011-11-18 expires: never usage: A
[ full ] (1). Pierre Schmitz (Arch Linux Master Key) <[email protected]>
I got to go now I will try gpg key edit later. If someone knows what to do please help.
Thanks

Usr/bin/pacman-key: line 615: printf: write error: Broken pipe

I've got some instances of same error from pacman which I think is abnormal when I tried to upgrade pacman-keyring via "pacman -Syu".
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
What action should I take for the errors to maintain my system?
Searching the web and this forum won't answer my question...
The quotation of pacman.log of the upgrade sesson which evoked pacman-keyring upgrading is below:
[2013-04-20 22:04] [PACMAN] Running 'pacman -Syu'
[2013-04-20 22:04] [PACMAN] synchronizing package lists
[2013-04-20 22:04] [PACMAN] starting full system upgrade
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 1 valid: 5 signed: 64 trust: 0-, 0q, 0n, 5m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 2 valid: 64 signed: 1 trust: 64-, 0q, 0n, 0m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Updating trust database...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [PACMAN] upgraded archlinux-keyring (20130224-1 -> 20130406-1)
[2013-04-20 22:05] [PACMAN] upgraded bash-completion (2.0-3 -> 2.1-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generating locales...
[2013-04-20 22:05] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] ja_JP.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generation complete.
[2013-04-20 22:05] [PACMAN] upgraded glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded binutils (2.23.2-1 -> 2.23.2-2)
[2013-04-20 22:05] [PACMAN] upgraded m4 (1.4.16-2 -> 1.4.16-3)
[2013-04-20 22:05] [PACMAN] upgraded bison (2.7-1 -> 2.7.1-1)
[2013-04-20 22:05] [PACMAN] upgraded curl (7.29.0-2 -> 7.30.0-1)
[2013-04-20 22:05] [PACMAN] upgraded expat (2.1.0-1 -> 2.1.0-2)
[2013-04-20 22:05] [PACMAN] upgraded freeglut (2.8.0-2 -> 2.8.1-1)
[2013-04-20 22:05] [PACMAN] upgraded gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gcc (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gpm (1.20.7-1 -> 1.20.7-2)
[2013-04-20 22:05] [PACMAN] upgraded harfbuzz (0.9.14-1 -> 0.9.16-1)
[2013-04-20 22:05] [PACMAN] upgraded isl (0.11.1-1 -> 0.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded kmod (12-1 -> 13-1)
[2013-04-20 22:05] [PACMAN] upgraded libldap (2.4.34-1 -> 2.4.35-1)
[2013-04-20 22:05] [PACMAN] upgraded krb5 (1.11.1-1 -> 1.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded lib32-glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded lib32-gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded libcap (2.22-3 -> 2.22-4)
[2013-04-20 22:05] [PACMAN] upgraded libpng (1.5.14-1 -> 1.5.15-1)
[2013-04-20 22:05] [PACMAN] upgraded libtasn1 (3.2-1 -> 3.3-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'default'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'fallback'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux-fallback.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [PACMAN] upgraded linux (3.8.5-1 -> 3.8.7-1)
[2013-04-20 22:05] [PACMAN] upgraded orc (0.4.16-1 -> 0.4.17-1)
[2013-04-20 22:05] [PACMAN] upgraded perl (5.16.3-1 -> 5.16.3-2)
[2013-04-20 22:05] [PACMAN] upgraded psmisc (22.19-1 -> 22.20-1)
[2013-04-20 22:05] [PACMAN] upgraded sqlite (3.7.16.1-1 -> 3.7.16.2-1)
[2013-04-20 22:05] [PACMAN] upgraded sudo (1.8.6.p7-2 -> 1.8.6.p8-1)
[2013-04-20 22:05] [PACMAN] upgraded systemd (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded systemd-sysvcompat (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded tar (1.26-2 -> 1.26-3)
[2013-04-20 22:05] [PACMAN] upgraded wayland (1.0.6-1 -> 1.1.0-1)
Thanks in advance!

I just encountered the same issue with the latest update. I never had something similar to this:
:: Retrieving packages ...
archlinux-keyring-20130525-2-any 367,2 KiB 1023K/s 00:00 [################################################################] 100%
linux-3.9.5-1-x86_64 45,5 MiB 1015K/s 00:46 [################################################################] 100%
linux-headers-3.9.5-1-x86_64 5,6 MiB 1117K/s 00:05 [################################################################] 100%
gnome-bluetooth-3.8.1-2-x86_64 835,0 KiB 955K/s 00:01 [################################################################] 100%
gnome-documents-3.8.3-1-x86_64 305,0 KiB 1034K/s 00:00 [################################################################] 100%
vlc-2.0.7-2-x86_64 7,6 MiB 1162K/s 00:07 [################################################################] 100%
(6/6) checking keys in keyring [################################################################] 100%
(6/6) checking package integrity [################################################################] 100%
(6/6) loading package files [################################################################] 100%
(6/6) checking for file conflicts [################################################################] 100%
(6/6) checking available disk space [################################################################] 100%
(1/6) upgrading archlinux-keyring [################################################################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
-> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
-> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
-> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
-> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...

Pacman-key wiki: Incorrect information

Good Morning all
The new pacman-key wiki has some misleading information within it, that should be corrected/clarified.
https://wiki.archlinux.org/index.php/Pa … e_checking
specifically
Edit /etc/pacman.conf and uncomment the following line under [options]:
SigLevel = Never
try it. The repositories are below this line and therefore the parser takes the last invocation of the SigLevel (global) option at a local level and doesn't honour the setting. You also need to comment any 'SigLevel' lines within the [core], [community] or [extra] repositories.
It should be clarified because it causes confusion.
Thanks
GregW
Last edited by GregW (2012-01-25 10:52:44)

It is a wiki... edit it.
You do not have permission to edit this page, for the following reasons:
The action you have requested is limited to users in the group: Users.
You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences.
You can view and copy the source of this page:
Oh well, nevermind, i've mentioned it.

Pacman-key problem

A new install from September CD iso. I went through install process but dumped at package install with unsigned or corrupted package error.
I burned another disc, same problem, restarted but installed Base only (I initially tried base & base-devel) to get a working box, and then updated this.
Rebooted and attempted to install base-devel, but still unsigned package error.
Next I used pacman -Sc to remove uninstalled packages (in case a corrupt package was in cache) but the same result. I changed mirror, but this did not resolve problem.
Next step was deleting gnupg & rebuilding (pacman-key --init, etc) but still unsigned package/corrupt error when I tried to install base-devel.
I installed each package in group individually, and found the error came with cloog, followed further and found dependency isl-0.10.1-1 was unsigned/corrupt package. Looking through forums, news and don't see anything regarding this so (giving that this iso has been around a week or two) I assume the problem is at my end somewhere.
Installed links & downloaded package, installed with pacman -U (this suggests that the package was not corrupt) and then installed cloog, followed by rest of base-devel.
What I don't understand is isl, cloog, gcc all have the same maintainer and therefore (presumably) signed by the same person. Why should I get an unsigned error for just one of the maintainers' packages?

Thanks for your thoughts, this was a fresh installation of the latest CD ISO. I downloaded/burned a second one with the same result.
Base-devel would not install as isl-0-10.1-1 was not securely signed (according to my installation).
I was able to download isl package and install, when 'pacman -S base-dev' worked, and system is now running fine. (just have to sort out this 'windows' printer now - thanks HP)

Pacman-key --edit-key without any TTY

Hi, I want to enable package signing on my vServer.
The problem is there is no TTY available.
# LANG=C pacman-key --edit-key 0x6AC6A4C2 ...
gpg: cannot open tty `/dev/tty': No such file or directory
==> ERROR: The key identified by 0x6AC6A4C2 could not be edited.
After adding "no-tty" to gpg.conf:
gpg: Sorry, no terminal at all requested - can't get input
==> ERROR: The key identified by 0x6AC6A4C2 could not be edited.
Please help me to solve this.
Thanks
- Radioactiveman

I have copied the gnupg directory from my PC to the server but that should be just a workaround.
Does nobody have an idea?

Pacman-key

The tone and remarks concerning pacman-key in the wiki indicate PGP signing is upcoming(although not yet default).
Not really needing such a system if I utilize pacman for upgrades regularly, I find it not a welcome change.
I wonder, for example, if a custom raid boot is utilized not utilizing user but only root will not accept the pacman-key system.
This seems to violate the KISS principle as well making the system more complex and subject to interface whammies not yet envisioned.
Attempting to upgrade this date resulted in no package upgrade w/o pacman-key.
If I try to upgrade w/o pacman-key included...... what then?
Can I disregard pacman-key and run ---Syuf....to upgrade? Am I shut off from upgrades w/o pacman-key?

man pacman wrote:
The SigLevel directive is valid in both the [options] and repository sections. If used in [options], it sets a default value for any repository that does not provide the setting.
* If set to Never, no signature checking will take place.

Mail: choosing one of multiple valid keys to sign

If I have multiple, valid keys for signing an email message, how do I chose which one Mail should use? If possible, I'd like to configure this on a per-message basis.
Thanks in advance,
Joe

Hi Balaji bhau
Just maintain the Overhead group in FG material master.. It will be done.. This too is required, if you want to charge diff overhead for diff FG.... If your overhead rate is same across, you dont even need Overhead group
Assign a costing sheet to your Valuation Variant....
If you want to apply diff OH to diff RM based on FG, then
1. Then assign Origin Group in RM Master In the Costing sheet BASE, use Cost Ele & Origin Group
2. Maintain Org Group X in RM A, Org Grp Y in RM B
And
Ovh Grp 10 in FGA & Ovh Grp 20 in FG B
you can maintain 10% Ovh on RM A and 7% on RM B for FG A & 20% Ovh on RM A and 17% on RM B for FG B
Refer Std Costing Sheet A00001 for your requirement...
Br, Ajay M

Which way is better to reverse a key figure sign, update rule or KF prop.?

We are trying to reverse a key figure sign and have got two options:
1. In Update Rule by using formula to make this key figure * 1-, or
2. In key figure property of query design mode, there is a checkbox of "Reverse +/- Signs".
Which one is better for the above two options?
Thanks
Message was edited by: Kevin Smith

Hi,
1. In Update Rule by using formula to make this key figure * 1-, or
A: If you want to update data permanently in Data Targets then go for update rules.
2. In key figure property of query design mode, there is a checkbox of "Reverse +/- Signs".
A: The data is not updated in Data Targets but while displaying in Reports it will display the sign.
That is upto you and business requirements.
Thanks
REddy

Circular: can't install libusb-compat for `pacman-key --init` [SOLVED]

So like a lot of people on here have upgraded to pacman 4.
I can't run `pacman-key --init` to update the keyring:
[stuart@myhost ~]$ sudo pacman-key --init
Password:
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
chmod: cannot access `/etc/pacman.d/gnupg/trustdb.gpg': No such file or directory
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
==> Updating trust database...
gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
And because of signature issues can't install libusb-compat:
[stuart@myhost ~]$ sudo pacman -S libusb-compat
Password:
resolving dependencies...
looking for inter-conflicts...
Targets (1): libusb-compat-0.1.3-2
Total Installed Size: 0.06 MiB
Net Upgrade Size: -0.02 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [######################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
error: GPGME error: Invalid crypto engine
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Last edited by Skipper_the_eye_child (2012-01-26 19:24:00)

That worked - thanks. It'd have helped had I remembered to write over pacman.conf of course! I've not done any mainentance for while, got a little rusty i'm afraid.
Last edited by Skipper_the_eye_child (2012-04-11 14:02:52)

[SOLVED] [pacman] My 'pacman-key --init' issue

pacman-key --init
gpg: Generating pacman keychain master key...
Not enough random bytes available. Please do some other work to give
the OS a chance to collect more entropy! (Need 211 more bytes)
Well, I thought that I could resolve it using random bytes from RANDOM.ORG (http://www.random.org/, in particularly http://www.random.org/bytes/), a really useful website.
Is it a good solution, or is it mandatory to generate random bytes using my PC? And in that case, how can I use random bytes generated from that site?
Last edited by metre (2011-10-14 09:48:31)

teratomata wrote:
hussam wrote:
I installed pacman 4.0 from testing. I did pacman-key --init
but now I can't install anything again
trying to install hplip
Proceed with installation? [Y/n] y
(1/1) checking package integrity [####################################] 100%
error: hplip: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-20? [Y/n] y
(1/1) checking package integrity [####################################] 100%
error: hplip: signature from "Eric Belanger <[email protected]>" is unknown trust
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
I found that my pacman.conf didn't get updated, but once I moved /etc/pacman.conf.pacnew to /etc/pacman.conf, everything worked.
I just wanted to say thanks teratomata. I did everything that was mentioned and was continually being asked if I wanted to import keys. Moved pacman.conf.pacnew to pacman.conf and everything works great!

Generation of 1024 bits key certificate signing request-sun one app srvr 7

Kindly help to generate 1024 bits key certificate signing request in sun one application server 7. The problem faced by me is that during csr generation the key lengh is 512 as this is the default value.Now i would like to change this default value and would like to generate a key with length 1024.Kindly help me.
Thanks in advance
Vishnu Priyan

OK, post a new Topic, title it Need help with self-signed certificate
Before you post, search the forums for the problem. Do the footwork.
Then, take your time, post exactly which of these steps you have taken, what the results were, and exactly where you are having problems, what the exact problem is (error message, whatever).
You are going to have much better response if someone can easily figure out what the problem you are having is. If you look at this thread, you will see "I have tried these 10 steps and they don't work". You are going to get nowhere with that.
I have to sleep now, good luck.

Pacman-key isn't working

pacman-key --init
gpg: Generating pacman keyring master key...
gpg: agent_genkey failed: End of file
gpg: key generation failed: End of file
gpg: Done
==> Updating trust database...
gpg: no need for a trustdb check
Whoa... I was googling around and no one seems to have encountered this problem before. I had JUST chrooted into the environment to install:
I was following this pretty carefully as far as I can tell:
https://wiki.archlinux.org/index.php/In … ting_Linux
Any guesses? I tried following the tips on dbus etc. None of these tips seemed helpful cuz none of those files exist. This is just the bootstrap installer.
Thanks, Oh MySQL !!

Did you try generating more entropy?
https://wiki.archlinux.org/index.php/Pa … he_keyring

Pacman-key local sign

Similar Messages

Maybe you are looking for