Hi Ralf,
sure, it's not a problem to receive a new key.
But the whole point in signing archives at all is that I want to know
who's key it is before accepting it.
It doesn't make much sense to just blindly accept an unknown key, especially
when you regularly build a package from the same source.
When the signature suddenly changes, you should at least inquire why,
don't you think? ;)
regards
Bernhard
On 27/05/17 23:55, Ralf Mardorf wrote:
On Sat, 27 May 2017 19:36:11 +0200, Bernhard Landauer wrote:
Yes, meanwhile I have looked it up and found that it belongs to
7B96E8162A8CF5D1
Sorry. All good!
Earlier today I build
[rocketmouse@archlinux ~]$ uname -a
Linux archlinux 4.9.30-rt19-1-rt-pussytoes #1 SMP PREEMPT RT Sat May 27 12:44:27 CEST 2017 x86_64 GNU/Linux
it already required to refresh the key. For cases like this I added an
alias...
[rocketmouse@archlinux ~]$ grep "alias gkey=" .bashrc
alias gkey='gpg --keyserver hkp://pgp.uni-mainz.de --recv-keys'
...so just running
[rocketmouse@archlinux ~]$ gkey 4FE5E3262872E4CC
...did the trick. When building from upstream and verifying against a
signature, this happens all the times ;).
Regards,
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
