| Message ID | 20180627174435.31800-1-alistair.francis@wdc.com |
|---|---|
| Headers | show |
| Series | riscv-pull queue | expand |
On 27 June 2018 at 18:44, Alistair Francis <alistair.francis@wdc.com> wrote: > The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1: > > Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100) > > are available in the Git repository at: > > git@github.com:alistair23/qemu.git tags/pull-riscv-pull-20180627 > > for you to fetch changes up to e5f5e16b67dc8a342f937bc00ebb2a6475e35050: > > hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device (2018-06-27 10:35:19 -0700) > Something strange is up with the key used to sign this: $ gpg --recv-keys 7048B74B4C1B39E4 gpg: requesting key 0x7048B74B4C1B39E4 from hkp server keys.gnupg.net gpg: key 0xE48E3BC2C123ED93: no valid user IDs gpg: this may be caused by a missing self-signature gpg: Total number processed: 1 gpg: w/o user IDs: 1 thanks -- PMM
On 06/28/2018 01:52 PM, Peter Maydell wrote: > On 27 June 2018 at 18:44, Alistair Francis <alistair.francis@wdc.com> wrote: >> The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1: >> >> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100) >> >> are available in the Git repository at: >> >> git@github.com:alistair23/qemu.git tags/pull-riscv-pull-20180627 >> >> for you to fetch changes up to e5f5e16b67dc8a342f937bc00ebb2a6475e35050: >> >> hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device (2018-06-27 10:35:19 -0700) >> > > Something strange is up with the key used to sign this: > > $ gpg --recv-keys 7048B74B4C1B39E4 > gpg: requesting key 0x7048B74B4C1B39E4 from hkp server keys.gnupg.net > gpg: key 0xE48E3BC2C123ED93: no valid user IDs > gpg: this may be caused by a missing self-signature > gpg: Total number processed: 1 > gpg: w/o user IDs: 1 It seems the SKS keyserver pool is having some problem: https://sks-keyservers.net/status/ $ host keys.gnupg.net keys.gnupg.net is an alias for hkps.pool.sks-keyservers.net. ... hkps.pool.sks-keyservers.net has address 18.191.65.131 hkps.pool.sks-keyservers.net has address 37.191.226.104 ... Except these 2 IP, all other failed via hkp or http (as of tod: The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Also: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /pks/lookup. Reason: Error reading from remote server $ gpg --keyserver hkp://18.191.65.131 --recv-keys 7048B74B4C1B39E4 gpg: key E48E3BC2C123ED93: public key "Alistair Francis <alistair@alistair23.me>" imported gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg: depth: 0 valid: 4 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 4u gpg: depth: 1 valid: 3 signed: 18 trust: 0-, 0q, 0n, 0m, 3f, 0u gpg: depth: 2 valid: 16 signed: 6 trust: 10-, 6q, 0n, 0m, 0f, 0u gpg: next trustdb check due at 2018-09-03 gpg: Total number processed: 1 $ git tag -v pull-riscv-pull-20180627 object e5f5e16b67dc8a342f937bc00ebb2a6475e35050 type commit tag pull-riscv-pull-20180627 tagger Alistair Francis <alistair.francis@wdc.com> 1530121274 -0700 gpg: Signature made Wed 27 Jun 2018 02:41:26 PM -03 gpg: using RSA key 100E2F7FE47ABA5024FF1B5B7048B74B4C1B39E4 gpg: Good signature from "Alistair Francis <alistair@alistair23.me>" gpg: aka "Alistair Francis <alistair23@gmail.com>" Primary key fingerprint: 29E0 5927 63B1 DA8C 8399 75FE E48E 3BC2 C123 ED93 Subkey fingerprint: 100E 2F7F E47A BA50 24FF 1B5B 7048 B74B 4C1B 39E4
On 28 June 2018 at 22:35, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote: > On 06/28/2018 01:52 PM, Peter Maydell wrote: >> On 27 June 2018 at 18:44, Alistair Francis <alistair.francis@wdc.com> wrote: >>> The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1: >>> >>> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100) >>> >>> are available in the Git repository at: >>> >>> git@github.com:alistair23/qemu.git tags/pull-riscv-pull-20180627 >>> >>> for you to fetch changes up to e5f5e16b67dc8a342f937bc00ebb2a6475e35050: >>> >>> hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device (2018-06-27 10:35:19 -0700) >>> >> >> Something strange is up with the key used to sign this: >> >> $ gpg --recv-keys 7048B74B4C1B39E4 >> gpg: requesting key 0x7048B74B4C1B39E4 from hkp server keys.gnupg.net >> gpg: key 0xE48E3BC2C123ED93: no valid user IDs >> gpg: this may be caused by a missing self-signature >> gpg: Total number processed: 1 >> gpg: w/o user IDs: 1 > > It seems the SKS keyserver pool is having some problem: > https://sks-keyservers.net/status/ > The server is temporarily unable to service your request due to > maintenance downtime or capacity problems. Please try again later. Hmm, there does seem to be something up with the pool. On the other hand: > $ gpg --keyserver hkp://18.191.65.131 --recv-keys 7048B74B4C1B39E4 This command with this specific server doesn't work for me (fails the same way with the "no valid user IDs" message), and using keyserver.ubuntu.com (which seems otherwise fine) also fails that way... thanks -- PMM
On Fri, Jun 29, 2018 at 2:41 AM, Peter Maydell <peter.maydell@linaro.org> wrote: > On 28 June 2018 at 22:35, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote: >> On 06/28/2018 01:52 PM, Peter Maydell wrote: >>> On 27 June 2018 at 18:44, Alistair Francis <alistair.francis@wdc.com> wrote: >>>> The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1: >>>> >>>> Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100) >>>> >>>> are available in the Git repository at: >>>> >>>> git@github.com:alistair23/qemu.git tags/pull-riscv-pull-20180627 >>>> >>>> for you to fetch changes up to e5f5e16b67dc8a342f937bc00ebb2a6475e35050: >>>> >>>> hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device (2018-06-27 10:35:19 -0700) >>>> >>> >>> Something strange is up with the key used to sign this: >>> >>> $ gpg --recv-keys 7048B74B4C1B39E4 >>> gpg: requesting key 0x7048B74B4C1B39E4 from hkp server keys.gnupg.net >>> gpg: key 0xE48E3BC2C123ED93: no valid user IDs >>> gpg: this may be caused by a missing self-signature >>> gpg: Total number processed: 1 >>> gpg: w/o user IDs: 1 >> >> It seems the SKS keyserver pool is having some problem: >> https://sks-keyservers.net/status/ > >> The server is temporarily unable to service your request due to >> maintenance downtime or capacity problems. Please try again later. > > Hmm, there does seem to be something up with the pool. On > the other hand: > >> $ gpg --keyserver hkp://18.191.65.131 --recv-keys 7048B74B4C1B39E4 > > This command with this specific server doesn't work for me > (fails the same way with the "no valid user IDs" message), > and using keyserver.ubuntu.com (which seems otherwise fine) > also fails that way... I'm not sure what else to do. I have submitted it to all of those key servers through GPG and through the web interface. I never see an error, but it doesn't show up under the web search. Can you import it manually? The armour export is below: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2 mJMEWjNEzBMFK4EEACMEIwQAqL2RYVgUJ4UWEJbRAONWJmYGDBfl659Y5FRWfjYu fBMZrj9DQarDC/P+QLOrBuwTmrBxXfg+/erVQKwYWDdnJG8AJ2m8Rli3wpYrxl/i XqvEfKJmh6a1ZUiBZ7Ldnr0eNGzhVUWSyrAU+ImGSOutHUS8ytH3ZOeDOz2lj2kA j6XYC+W0KUFsaXN0YWlyIEZyYW5jaXMgPGFsaXN0YWlyQGFsaXN0YWlyMjMubWU+ iNwEExMKAEECGwMFCQlmAYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AWIQQp4Fkn Y7HajIOZdf7kjjvCwSPtkwUCWjNE/AIZAQAKCRDkjjvCwSPtkyK6AgkBHJA7++aK aeqvupdIPM87Yo2C7h+jsGVgTdr2N5uKS93xNOyn8rkAbGJV6GQXqjuEZgp1Ukvi 7M4o0Xk6XumOri8CB2T+v1CJedxNnNSE6rCdlaqJOxEKHA9oX8btksgpozRCbIMc MZUMHadTc1GMMyoKg84hmLbk1vHtne4WQb3x6e/aiQEzBBMBCgAdFiEE867fg8U6 1eISTHkpuQvHq+fEHmUFAlszyGsACgkQuQvHq+fEHmVpQwf/ZEL7ww59KB7xPb5N YuPVaFNZ2VsFPsaX3IZGi82Rgn7c2ZXcvQvv6V5nfn4zwK8m2MnTENBc4U+VJ+WT /oump7npWaooJxTE8M9YE1pR8SaXdvPTzDCDjDVk52fX6/p/IFcjQnAoeKD3W5iL KvS6i5yynEv1Onl7E5HFte72kmUhE4NhDaS0w6wataS75xdJapL+Ehh7dV1V9INJ KqsIZr3KO+uHqgqhY1k6eT8LKZl4o2GYkNGQLvzRRuAXicICexKNZHKyrPcP3fZY WCYtgE5BjckyW2sjdozg9q9no6DFde/p4Yz6JC5TJSpNBx9CSwqXOkjMNMujLRX+ mmJif7QnQWxpc3RhaXIgRnJhbmNpcyA8YWxpc3RhaXIyM0BnbWFpbC5jb20+iNoE ExMKAD4WIQQp4FknY7HajIOZdf7kjjvCwSPtkwUCWjNE6AIbAwUJCWYBgAULCQgH AgYVCAkKCwIEFgIDAQIeAQIXgAAKCRDkjjvCwSPtkxtHAgkBqlNesB/2Wr/j0Cd4 bhjwnpdWO5BGsKuLCBlnEgts6BEh5z5w7OEmgCYoEHTro6Q119D1hjmG5sLUn5AR +SeVQ/8CCQGNuK/oIFS6MIXm66vrC1QwPyS5pdeXyZXKLK7sue515T86huQ0wdae dt+UubuhLFNuP8MOZHWm5rum1R9X65TkTokBMwQTAQoAHRYhBPOu34PFOtXiEkx5 KbkLx6vnxB5lBQJbM8inAAoJELkLx6vnxB5lptQH+wUiSrZcrH2+n7Qlqe2e5u/s 8WWPS4+i8cxtZ6gpchUyTlaKRowFs+s6tAedwl5+gDZiQCxTwIP6fBxZeIC+Fen6 3zpzaE/EnxsqIAAa/zO30TIAHRqFp++m1DeZbarIho41ZY3A9X96UgN6jqj4zhVK UTkkIFBye/MpYFB7xoMPuU90MgAtOPif4/vejXb3oYbllDXaomjfInqPnCiZc/1b ApeQrIIlTVXrgExDVGQpHNQEHROtqjjwkhbKSPBwQ//rVPdiu61icJgcL8MVQfvP IP5Vidi/X88xmlyWm+dCeTv62wRl9bCa4NQo3yL6M0uyaSS0j84ebVXHKTmxCyi5 AQ0EWjNF3wEIAMlri8jeUQabINXnrQmCAZMRTwJK/yqkN0mr7IJYLl77oTJm3ozO dqMNCfidhH7XWb6mLRvpALffDQ3Wx1O7Q0zBe4M2SG2vGnO/y8O2FnXyKTDNJsD3 S2JA0l7UT9dNQFymcf73bXsECkz40d8xZS/QhO6fcynMwtkzITq3QDE3f5mk4FbH 1gYIftRRSzaO8cxbRuRroTs4+t7GgoWqVDpzr0ohoNqnFLqB5WHStH4ONhnLCYmk L7eYTW97CvK5UqrZow2mzFCv+U87Sel6tcAGzF3NxB0+7aEiaJpYoBE1YjOjdOY7 whT5JqYKn7jScDuMBSkyvBuTKM3PsdJsqHEAEQEAAYi7BBgTCgAgFiEEKeBZJ2Ox 2oyDmXX+5I47wsEj7ZMFAlozRd8CGwwACgkQ5I47wsEj7ZNAhwIJAdfX/7+INmge vMRtWRHoagkJgqxx9CfekHQceEgoDTIIY0HSFRH4KIkps8zVqMpaZp6f6bAWXk7t SeSkTUXokzu5AgYhLTi/r0yoSpzMvnk770DLy4APwbs76cMt93BrcTUFtBlemYjf oyylka9240l4re42UWmtN6XWjtt4LTiA1y8Pi7kBDQRaM0XkAQgAvyahH9xJ6X8m Mce6tUNlHRoOuqLucyMTOIkRQmmUKSyCJNAAG+Wcrqda9k5G1R6Wz68joBY+LlwD 1J+UsA4mKrNrBrvrkj/vrjZ2pFCrzI6edYP8s492xc3Fty/5o3IyF9uyVoY+shgK WC5tviJqyi0Isnbxygc/AyKPCa83eNz+ZWewHqvcxsdWzMAHWuTRqWZ0D/Nx26/G dgxiLwgs7G2/f+iXe8MyWK1Shg++YJ3PNEZdSfAGJDUTgJXsIxi1o/Sd8VK3fT0N 7EO+U4cl3AIz2iN934ScIc3gODp6XrpxujkMbk4vPJ3N8cz9BNvml/Oj5btcufoZ 6gTVa8zbeQARAQABiQHyBBgTCgAgFiEEKeBZJ2Ox2oyDmXX+5I47wsEj7ZMFAloz ReQCGwIBQAkQ5I47wsEj7ZPAdCAEGQEIAB0WIQQQDi9/5Hq6UCT/G1twSLdLTBs5 5AUCWjNF5AAKCRBwSLdLTBs55ANNCACDuAUcxBSLwCxRctsfMksCCUUmOAV9UK6Z HmiqhWOBBl/1aw3mEEPsPucJ2rvdd0g4ntmka8J8rJVzRsJHv7z4eqAqET8rxFTv 4LSbckpBbSz1qHXklG1o0UVlIwVwVf6Wrs3aADy0XBGXqungR8Un5YpOmOJ7OvKq fyJv/YgjUYaOtiPe0Re6J6QEqI+FC2e9lq4lOzA3Kwq09PSMbUL/gR7NGlQKgrQ2 6b71hz2+aOZGCygG4RZUON6mUb0k/Extj7h4NIXyTXXBDwNnR2qVWriDLVewQ8EO yn/KXIoneR/D9nJHOIEmx9q8OYmc2TpxgQI8rz7uvjvuaw4XtH41ul4CCQFnkD5m Qq4yP9xZgFiXYWFWdttV+8Kqlx2hH+hQFHmGFyNvwfty9JSegyu8iZ8gsKTy51he 2HqjVzYiImBrqa6i0QIJAY9e64iH+3PmjOYGsL5Hr5QSm0oyJG+/7KMRfvCSg/Qp FmfzHamkd0ublxjF9ROxGdFwpRiNSOZ8XRd2YrCzZg/kuQENBFozRewBCACy2ayw QK5cC6FO6CQdh7HhMJMLvT7QLerZ5FQnCfh1OG6wsMgQJbVYdr7La3tap4vNkhe6 jIPDko/ps0k6AhK8mYnP5bXumpzLHAzs3xYYHYmQ3GWDSQxX0ajbgAOSdLJF8vNM NZBzm3AjPokX2/r0L8bMRSJ5a2QGXuy2ThrimLeojbYlTw6zajyFSLhHwkmiUCIh uqRxe9UjLeVTq4Ejmm4NwvTA6cwRnpyndv05rkM5sDyNd9b4K5Y3eSZ2Yk8FBPPA pWhPa0Oq8vjOu4oqacOBgY5cwvTCpNwMKYBFOmYhrZ8b6swk0fa/xK/C9zXvF69r O+EmfRjJr6mk9nO5ABEBAAGIuwQYEwoAIBYhBCngWSdjsdqMg5l1/uSOO8LBI+2T BQJaM0XsAhsgAAoJEOSOO8LBI+2TanQCCKi9gcTCpHtgtJOimUuTsthuH/K7f/M2 ZFeNgIm0k6HfKjgDCZMbK6evpuLuTrdeekyT1W0MLJIWmh0j3eJz31kZAgkBDOBs Ezo6jhKug5aPbQ71GAy8tcKK783Ye2Ei0UCgTXGNdNZoPiYdhO7IX/QmNdMCtQ9R zafpeVkcoSpABQrI2UQ= =xMq1 -----END PGP PUBLIC KEY BLOCK----- Alistair > > thanks > -- PMM
On 29 June 2018 at 15:13, Alistair Francis <alistair23@gmail.com> wrote:
> Can you import it manually? The armour export is below:
Aha. I tried that, which didn't work either, which prompted
me to try --verbose, which says:
e104462:xenial:qemu-for-merges$ gpg --verbose --import /tmp/alistair.gpg
gpg: armour header: Version: GnuPG v2
gpg: can't handle public key algorithm 19
gpg: pub 0E/0xE48E3BC2C123ED93 2017-12-15 Alistair Francis
<alistair@alistair23.me>
gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user
ID "Alistair Francis <alistair@alistair23.me>"
gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user
ID "Alistair Francis <alistair23@gmail.com>"
gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm
gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm
gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm
gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis
<alistair@alistair23.me>"
gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis
<alistair23@gmail.com>"
gpg: key 0xE48E3BC2C123ED93: skipped subkey
gpg: key 0xE48E3BC2C123ED93: skipped subkey
gpg: key 0xE48E3BC2C123ED93: skipped subkey
gpg: key 0xE48E3BC2C123ED93: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg: w/o user IDs: 1
So the problem is that your key is using some algorithm
that's too newfangled for my gpg to cope with...
thanks
-- PMM
On Fri, Jun 29, 2018 at 7:21 AM, Peter Maydell <peter.maydell@linaro.org> wrote: > On 29 June 2018 at 15:13, Alistair Francis <alistair23@gmail.com> wrote: >> Can you import it manually? The armour export is below: > > Aha. I tried that, which didn't work either, which prompted > me to try --verbose, which says: > > e104462:xenial:qemu-for-merges$ gpg --verbose --import /tmp/alistair.gpg > gpg: armour header: Version: GnuPG v2 > gpg: can't handle public key algorithm 19 > gpg: pub 0E/0xE48E3BC2C123ED93 2017-12-15 Alistair Francis > <alistair@alistair23.me> > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user > ID "Alistair Francis <alistair@alistair23.me>" > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user > ID "Alistair Francis <alistair23@gmail.com>" > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis > <alistair@alistair23.me>" > gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis > <alistair23@gmail.com>" > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: no valid user IDs > gpg: this may be caused by a missing self-signature > gpg: Total number processed: 1 > gpg: w/o user IDs: 1 > > So the problem is that your key is using some algorithm > that's too newfangled for my gpg to cope with... Hmm... I do use gpg2, but it's just an RSA2048 key. Is it possible to update your GPG? Otherwise I can try generating a new key just for QEMU PRs. Alistair > > thanks > -- PMM
On 06/29/2018 11:21 AM, Peter Maydell wrote: > On 29 June 2018 at 15:13, Alistair Francis <alistair23@gmail.com> wrote: >> Can you import it manually? The armour export is below: > > Aha. I tried that, which didn't work either, which prompted > me to try --verbose, which says: > > e104462:xenial:qemu-for-merges$ gpg --verbose --import /tmp/alistair.gpg > gpg: armour header: Version: GnuPG v2 > gpg: can't handle public key algorithm 19 > gpg: pub 0E/0xE48E3BC2C123ED93 2017-12-15 Alistair Francis > <alistair@alistair23.me> > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user > ID "Alistair Francis <alistair@alistair23.me>" > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user > ID "Alistair Francis <alistair23@gmail.com>" > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm > gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis > <alistair@alistair23.me>" > gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis > <alistair23@gmail.com>" > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: skipped subkey > gpg: key 0xE48E3BC2C123ED93: no valid user IDs > gpg: this may be caused by a missing self-signature > gpg: Total number processed: 1 > gpg: w/o user IDs: 1 > > So the problem is that your key is using some algorithm > that's too newfangled for my gpg to cope with... Oh indeed, this is a ECDH NISTP-521 public key!
On Fri, Jun 29, 2018 at 03:21:08PM +0100, Peter Maydell wrote: > On 29 June 2018 at 15:13, Alistair Francis <alistair23@gmail.com> wrote: > > Can you import it manually? The armour export is below: > > Aha. I tried that, which didn't work either, which prompted > me to try --verbose, which says: > > e104462:xenial:qemu-for-merges$ gpg --verbose --import /tmp/alistair.gpg > gpg: armour header: Version: GnuPG v2 > gpg: can't handle public key algorithm 19 This is an ECC algorithm, and only supported by gpg2 tool not gpg AFAICT. Regards, Daniel
On 29 June 2018 at 15:27, Alistair Francis <alistair23@gmail.com> wrote: > On Fri, Jun 29, 2018 at 7:21 AM, Peter Maydell <peter.maydell@linaro.org> wrote: >> So the problem is that your key is using some algorithm >> that's too newfangled for my gpg to cope with... > > Hmm... I do use gpg2, but it's just an RSA2048 key. Philippe says it's ECDH NISTP-521... > Is it possible to update your GPG? I don't believe any gpg(1) supports that algorithm. I'm not really keen on moving to gpg2 because I hear bad things about it... thanks -- PMM
On Fri, Jun 29, 2018 at 7:49 AM, Peter Maydell <peter.maydell@linaro.org> wrote: > On 29 June 2018 at 15:27, Alistair Francis <alistair23@gmail.com> wrote: >> On Fri, Jun 29, 2018 at 7:21 AM, Peter Maydell <peter.maydell@linaro.org> wrote: >>> So the problem is that your key is using some algorithm >>> that's too newfangled for my gpg to cope with... >> >> Hmm... I do use gpg2, but it's just an RSA2048 key. > > Philippe says it's ECDH NISTP-521... > >> Is it possible to update your GPG? > > I don't believe any gpg(1) supports that algorithm. > I'm not really keen on moving to gpg2 because I hear bad > things about it... Ok, I'll generate a new non-ECC key today and send a new PR. Alistair > > thanks > -- PMM
The following changes since commit 00928a421d47f49691cace1207481b7aad31b1f1: Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180626' into staging (2018-06-26 18:23:49 +0100) are available in the Git repository at: git@github.com:alistair23/qemu.git tags/pull-riscv-pull-20180627 for you to fetch changes up to e5f5e16b67dc8a342f937bc00ebb2a6475e35050: hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device (2018-06-27 10:35:19 -0700) ---------------------------------------------------------------- RISC-V: SoCify SiFive boards and connect GEM This series has three tasks: 1. To convert the SiFive U and E machines into SoCs and boards 2. To connect the Cadence GEM device to the SiFive U board 3. Fix some device tree problems with the SiFive U board After this series the SiFive E and U boards have their SoCs split into seperate QEMU objects, which can be used on future boards if desired. The RISC-V Virt and Spike boards have not been converted. They haven't been converted as they aren't physical boards, so it doesn't make a whole lot of sense to split them into an SoC and board. The only disadvantage with this is that they now differ to the SiFive boards. This series also connect the Cadence GEM device to the SiFive U board. There are some interrupt line changes requried before this is possible. ---------------------------------------------------------------- Alistair Francis (7): hw/riscv/sifive_u: Create a SiFive U SoC object hw/riscv/sifive_e: Create a SiFive E SoC object hw/riscv/sifive_plic: Use gpios instead of irqs hw/riscv/sifive_u: Set the soc device tree node as a simple-bus hw/riscv/sifive_u: Set the interrupt controler number of interrupts hw/riscv/sifive_u: Move the uart device tree node under /soc/ hw/riscv/sifive_u: Connect the Cadence GEM Ethernet device default-configs/riscv32-softmmu.mak | 3 +- default-configs/riscv64-softmmu.mak | 3 +- hw/riscv/sifive_e.c | 102 +++++++++++++++++------- hw/riscv/sifive_plic.c | 6 +- hw/riscv/sifive_u.c | 151 +++++++++++++++++++++++++++++------- hw/riscv/virt.c | 4 +- include/hw/riscv/sifive_e.h | 16 +++- include/hw/riscv/sifive_plic.h | 1 - include/hw/riscv/sifive_u.h | 25 +++++- 9 files changed, 241 insertions(+), 70 deletions(-)