GPG key notification

26 views
Skip to first unread message

Davíð Steinn Geirsson

unread,
Mar 28, 2018, 9:14:07 AM3/28/18
to qubes...@googlegroups.com
Hi all,

From now on I will sign my Qubes commits and tags with the key in
qubes_development_signing_key.asc, having keyID:
290B63F8D7014CC99C67FCA8D9EB1506562E15C3

Mail correspondence will be signed with the key in mail_key.asc, ID:
CA461E4D5CBBD55FB53B6F1F16FFCB5025BBEAE0

Both keys are signed by my master key which I have already used here
on the list, master_key.asc, ID:
A8ED3929A5EE962F207181E68F422CA1372523E0

I would appreciate if the master key could be added to my entry on the
Team page:
https://www.qubes-os.org/team/


I am about to submit some changes using the above Qubes signing key, so
I wanted to give a heads-up first.

Thanks & Best Regards,
Davíð

mail_key.asc
master_key.asc
qubes_development_signing_key.asc
signature.asc

Marek Marczykowski-Górecki

unread,
Mar 28, 2018, 9:25:39 AM3/28/18
to Davíð Steinn Geirsson, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Thanks for heads-up. Can you push them to some keyserver, so
signature-checker could fetch them automatically?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqxkFMACgkQ24/THMrX
1ywyuAf9GzWIR9MeUvkGxCNvHWoapsCYsDbiJi4wcnfHjH7C4PtYUJtlzUYDogYA
rgAKyl92atnrw4ZzE6OEiSp0OPFyjjODH54s78+e68buxYWLSVM0T/Ys6URt3yKb
5tWk6M9jWdYvtU5hkM/nF+JFI4O48Ig4eeR2f88zgz058USAhk4aAjH1cvaSijKD
apRntzB0ya9lVS+Q1hEPqopIik1lf3ldgvYSp1KyLeYhHpD9Tsh+76+KCj5xfs6R
f1pqDItmf3TrtcIg/w9vMZexl6H9M0by9e7cBiAatkqQyPFvaGzze6Oe7pcIqqcM
S3ICUK8kSPQlF1XxFJNMTl3LBe01yw==
=2F4i
-----END PGP SIGNATURE-----

Davíð Steinn Geirsson

unread,
Mar 28, 2018, 9:42:16 AM3/28/18
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
On Wed, Mar 28, 2018 at 03:25:17PM +0200, Marek Marczykowski-Górecki wrote:
> On Wed, Mar 28, 2018 at 01:14:04PM +0000, Davíð Steinn Geirsson wrote:
> > Hi all,
> >
> > From now on I will sign my Qubes commits and tags with the key in
> > qubes_development_signing_key.asc, having keyID:
> > 290B63F8D7014CC99C67FCA8D9EB1506562E15C3
> >
> > Mail correspondence will be signed with the key in mail_key.asc, ID:
> > CA461E4D5CBBD55FB53B6F1F16FFCB5025BBEAE0
> >
> > Both keys are signed by my master key which I have already used here
> > on the list, master_key.asc, ID:
> > A8ED3929A5EE962F207181E68F422CA1372523E0
> >
> > I would appreciate if the master key could be added to my entry on the
> > Team page:
> > https://www.qubes-os.org/team/
> >
> >
> > I am about to submit some changes using the above Qubes signing key, so
> > I wanted to give a heads-up first.
>
> Thanks for heads-up. Can you push them to some keyserver, so
> signature-checker could fetch them automatically?

Done :)

Is there some way to force a re-run of the codesigning check on the github
PR?
signature.asc

Marek Marczykowski-Górecki

unread,
Mar 28, 2018, 11:17:38 AM3/28/18
to Davíð Steinn Geirsson, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Mar 28, 2018 at 01:42:14PM +0000, Davíð Steinn Geirsson wrote:
> On Wed, Mar 28, 2018 at 03:25:17PM +0200, Marek Marczykowski-Górecki wrote:
> > On Wed, Mar 28, 2018 at 01:14:04PM +0000, Davíð Steinn Geirsson wrote:
> > > Hi all,
> > >
> > > From now on I will sign my Qubes commits and tags with the key in
> > > qubes_development_signing_key.asc, having keyID:
> > > 290B63F8D7014CC99C67FCA8D9EB1506562E15C3
> > >
> > > Mail correspondence will be signed with the key in mail_key.asc, ID:
> > > CA461E4D5CBBD55FB53B6F1F16FFCB5025BBEAE0
> > >
> > > Both keys are signed by my master key which I have already used here
> > > on the list, master_key.asc, ID:
> > > A8ED3929A5EE962F207181E68F422CA1372523E0
> > >
> > > I would appreciate if the master key could be added to my entry on the
> > > Team page:
> > > https://www.qubes-os.org/team/
> > >
> > >
> > > I am about to submit some changes using the above Qubes signing key, so
> > > I wanted to give a heads-up first.
> >
> > Thanks for heads-up. Can you push them to some keyserver, so
> > signature-checker could fetch them automatically?
>
> Done :)
>
> Is there some way to force a re-run of the codesigning check on the github
> PR?

Yes, there is, but not publicly available. Done.
Alternatively, it also recheck on any PR change. So for example
force-pushing the same commit with updated date will also work.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqxqpMACgkQ24/THMrX
1yz/vAf/ZmYlruA5OaeJSexKB5JdeF6KlJyyF060RSCUqT0WLgSijYuqvTMkGSJu
5SIYVJKpfu3rCPbImgBmHnWjQ5+NV75W+cxcQvGR6Yih8iPRHRXjcj/ywwM98/Uw
kj4r+3ttXmpLqZ6aZl/0MZIX4/SO/IuqAe4BydsgZfz00ohq1/uJQScN4giEdgBG
oYE9F6ZXJoW0FbGCJK6U2N+JlguvllejxyKzfArBH3FsZkvdmGkkJbpfckrbRi2l
m3l8AA2QxdNXtd41y0DbcTiGFkjk4wx9S/ew1CeUj+nkbnQfDNHIzlk5bpdfoetl
8YsVk/jMk5Vg5uUN3UI1N0jA/J+45Q==
=/L8e
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages