For the past six months, pacman's package verification features were turned off by default while we were figuring out the details of our public-key infrastructure. They have finally been enabled in pacman-4.0.3-2; when you upgrade, you will be prompted to run: pacman-key --init pacman-key --populate archlinux _____________________________________ Hello! Is it possible to run this commands remotely (ssh)? I have tried in different machines, and all of them seem to hang after saying "gpg: Generating pacman keychain master key..." Well, it is not hanged, after almost 30 minutes I can stop it with CTRL-C, and get a "gpg: signal interrupt caught ... exiting" Best Regards, Guillermo Leira
On 06/04/2012 10:36 PM, Guillermo Leira wrote:
For the past six months, pacman's package verification features were turned off by default while we were figuring out the details of our public-key infrastructure.
They have finally been enabled in pacman-4.0.3-2; when you upgrade, you will be prompted to run:
pacman-key --init
pacman-key --populate archlinux
_____________________________________
Hello!
Is it possible to run this commands remotely (ssh)? I have tried in different machines, and all of them seem to hang after saying
"gpg: Generating pacman keychain master key..."
Well, it is not hanged, after almost 30 minutes I can stop it with CTRL-C, and get a
"gpg: signal interrupt caught ... exiting"
Best Regards,
Guillermo Leira
create entropy, start copying some files, do a backup, do cat /dev/sda as root :D -- Ionuț
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/04/12 13:06, Ionut Biru wrote:
create entropy, start copying some files, do a backup, do cat /dev/sda as root :D
I *think* you're right. But perhaps pacman-key should give a clue that this is what's going on. On two of the three systems I ran this on, it completed within what seemed to me a reasonable time. On the third system, my "old" laptop (only a duo-core x86, boo-hoo), it took quite a while. I didn't do anything to "create" entropy, though I certainly could have, because I didn't have that hint. And it did *eventually* finish on its own. - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPzRZuAAoJELT202JKF+xpsRAP/3XO1TVMWRpY+qdHJ3dqT/qp Ez+jhkumVIRUR2LM9XMj5/tuhDSJX4tn5/evkh7BhD9KVb4R0gSLoTx7LEWfLhnI 7CUuI6c/cW3byqVO9PTaM9qgQ4Jsy9ooVO9kDvwWm7dXNuv07vY+pZ02JqikDlJC 3d4UxJcfub2Om/82jMnM/u83Ghwv2+2abI/VZ4G7ywnKOPihTMlxkUKcRZRqc/9z HOPILCOl4GCtjGTcQz22vthLPoGxl38m6JNb4KVnZ+DtYQB3qgoCHO6bNBkrw0Kd QdNxCMWvkAOehYM6eD2aV226g8krm6l3NY0QiTqGtaByZun7lJlDGeOVzseaNJmO 4TwaXsbK7iXcTIgLWHXm+1Xt2k9y8k5l8J3E26ux3oMswCSmU8tm19f+Xv6GrY++ dbqfa2koSjaRsZU+8s6PirwegmXyFGrMMl56KqTAOf8wKUVoG/kxeS/WPiJ8ZJv4 0IcTHintCcsNXI1TagQwewnu07h16E+Ms7d7qUemfCpLgHfOz+DfRYz4fznxpOHF dE0M1GYh2xWFzKJ5lJpQQ5mGtyg+c7vvKpEYheFvd7nVQmmdKIaSIhixwvlaqOqH IqtFSSQMP6HUsGJKMVl5hmryHyYnlvx6N4XYBHga5leXS+R+wx+ZhZ5NQamYwRb4 KzJNEvdak/Skv44/c1R4 =wwBy -----END PGP SIGNATURE-----
On Mon, Jun 4, 2012 at 10:11 PM, David Benfell <benfell@parts-unknown.org> wrote:
I *think* you're right. But perhaps pacman-key should give a clue that this is what's going on.
https://bugs.archlinux.org/task/28027 If you have time, please file this upstream if it haven't been filed in the mean time.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/04/12 15:46, Karol Blazewicz wrote:
On Mon, Jun 4, 2012 at 10:11 PM, David Benfell <benfell@parts-unknown.org> wrote:
I *think* you're right. But perhaps pacman-key should give a clue that this is what's going on.
https://bugs.archlinux.org/task/28027 If you have time, please file this upstream if it haven't been filed in the mean time.
The decision at that link seems to view this as an upstream problem and points to https://bugs.g10code.com/gnupg/ as upstream. But the latter link never mentions pacman. So I'm confused. - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPzXDyAAoJELT202JKF+xpj/IP/3sKbyfQWpM4E83py4YXUJWl D8m/D0YxtOmmwx4mRuHaRUNGI33pzy58kHnbDIHx9qXhG3WSJJjssqWf/Eft6Ycb 18yIW42DEz1pPR4M5s+7zwQK05J3VERCeAilCF/+3i19L09ZqZMeVzltRtK3CWdB Xe/2wjaBBDhick6MctEntMreCSRaIIqG9AMqOoyYQeqE9jBLNvtpqq9ia1iDI/ao w6BNCDmX2F9B190cfab1Rue8c3m230in04x2+nVL6stH0I+1ZL3wSB1mJwakWzPa MSwQmRhQ85Y0PnqQrgVQx3cSZsViMbyUlsrzBoW+dL3D7/U3HBpUebCwxY7OQ3fr jN0Aj+c+9yCawoC/0qRRxrGPRZfOpW9Na2kBOW60y5UXmEMiYWHqqmHkuxwT2BdK dWl2rM3vOn9lcnB7eAMqBG6tlPk3QxazF/uKx9E2AYI6kpavZ4xwbtSiFwXPugHa uFGaNjuNV/JnkO+Ot7/Sx4PT9jcSfwr5vPM3NOmqWhkoSM/OXkW6s/7odaSo7Uov oUwirrn/hJoXlqz/KRxGxahoz+N2Q6Ayfq/S7FYa9Qbw9xk5gLPfDrG2v1Sjjjkx KVXxgxI7F7JJIWGDOKVkqCFrC1C7+0pePzVtXvI5sFNXEcpiS8rKojmW3YUQapIi dSdfyeQNBjj2cRBjrrKC =Yzci -----END PGP SIGNATURE-----
On 05/06/12 12:37, David Benfell wrote:
On 06/04/12 15:46, Karol Blazewicz wrote:
On Mon, Jun 4, 2012 at 10:11 PM, David Benfell <benfell@parts-unknown.org> wrote:
I *think* you're right. But perhaps pacman-key should give a clue that this is what's going on.
https://bugs.archlinux.org/task/28027 If you have time, please file this upstream if it haven't been filed in the mean time.
The decision at that link seems to view this as an upstream problem and points to https://bugs.g10code.com/gnupg/ as upstream. But the latter link never mentions pacman. So I'm confused.
Because pacman has nothing to do with generating a key. It is all gnupg...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/04/12 19:39, Allan McRae wrote:
On 05/06/12 12:37, David Benfell wrote:
On 06/04/12 15:46, Karol Blazewicz wrote:
On Mon, Jun 4, 2012 at 10:11 PM, David Benfell <benfell@parts-unknown.org> wrote:
I *think* you're right. But perhaps pacman-key should give a clue that this is what's going on.
https://bugs.archlinux.org/task/28027 If you have time, please file this upstream if it haven't been filed in the mean time.
The decision at that link seems to view this as an upstream problem and points to https://bugs.g10code.com/gnupg/ as upstream. But the latter link never mentions pacman. So I'm confused.
Because pacman has nothing to do with generating a key. It is all gnupg...
Ah, but gnupg on its own advises that it needs entropy. I didn't see this message from pacman-key, so pacman-key would seem to be *suppressing* the message. If I'm getting all this right, then the decision to bump this upstream seems inappropriate. - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPzXM0AAoJELT202JKF+xpKVAP/16+yG55LbtF7g7msH2fqs4s VSOxH89elw226d9GfsEQu/36H5wWNdua++KOGpVLvj9pM1IWs4LGLsmyDSXSBMH6 PQyTNT8tRniBPpVzGWZJmD2kd1npzAaIrV7ds2tfVF6PA3wOJhwAFtR6wpUX7hw8 dA49X2YPRL40nMpVm7emuNbP1wyhbpVJJm58rbxloiPrfFYIorAbL6RMl7EtVP+W T1FsiIf1EahdInhNavfgvV+D2xdhmZPKw8v7s2MVA76VUwF0xB3iHCIEx/LZb6DP 1dlXsVwC3Hvfw3U+s9TaHjsxjXEVy9+qp4U/4BmpHED9UMsJC/4G+IWVwff7zJbd zDmQbVDC3QCQkf/GO/PqzUp+4YB4OpUCsqKdAmIxpAeZD8IWgBYcUuPQ0bTL2kDh 2aZdaGYGn1M+t4nxbXnD+LQloEjPCcftoEMLCWZMa/YKZNyhBUJAHLWBF/9Ic+QD HUikIGvy6cJ7sdLRCFoquolnwXPQ/LszBZ0M8MEaOv438Le38K9ZKVblw6qUrnwx YA0RPbVjkip/P33Coek2bpvjoVXZkzCAsg8XAPKpgO7RuMihPVob0KAnflAEhpBJ 6LCVeMK8cTkXHKEdn0SoP3VLbSI+B+a8EB12IsbrsaK0gB4qS46G1gU9vH05n8+D ZI11+6daTUCzDl/1FyMm =pBam -----END PGP SIGNATURE-----
participants (5)
-
Allan McRae
-
David Benfell
-
Guillermo Leira
-
Ionut Biru
-
Karol Blazewicz