-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Key transition statement, Tuesday, 16th November 2021

As my signing key expired on 14th of November and I could not extend the
expiration date nor create a new subkey, I have created a new key.

The old key is:

pub   rsa4096/AD5F960A256A04AF 2016-11-15 [SC]
      E19F5F87128899B192B1A2C2AD5F960A256A04AF
uid                 Johannes Ranke (Wissenschaftlicher Berater) <johannes.ranke@jrwb.de>
uid                 Johannes Ranke <jranke@uni-bremen.de>
sub   rsa3072/FCAE2A0E115C3D8A 2016-11-15 [S] [expired: 2021-11-14]
sub   rsa3072/AF83CE117FBB4C22 2016-11-15 [E] [expired: 2021-11-14]
sub   rsa4096/6399D8DF86443762 2016-11-15 [E]

The new key is:

pub   rsa4096/DC78B2DDEABC47B7 2021-11-16 [C] [expires: 2026-11-15]
      95C0FAF38DB3CCAD0C080A7BDC78B2DDEABC47B7
uid                 Johannes Ranke <johannes.ranke@jrwb.de>
sub   rsa3072/B8F25A8A73EACF41 2021-11-16 [S] [expires: 2026-11-15]
sub   rsa3072/8BA5BF1D9CFC354F 2021-11-16 [E] [expires: 2026-11-15]

I am signing this statement with the dated CRAN backport signing key from 2007
(hence using SHA1):

pub   dsa1024/06F90DE5381BA480 2007-02-15 [SC]
      6212B7B7931C4BB16280BA1306F90DE5381BA480
uid                 Johannes Ranke (CRAN Debian archive) <jranke@uni-bremen.de>

This signature in combination with the correct origin of the statement [1]
should give you some trust that it is authentic.

Let me know if you have comments or questions, and sorry for the inconvenience
caused.

Johannes

[1] https://jrwb.de/docs/key_transition_2021-11-16.asc

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQRiEre3kxxLsWKAuhMG+Q3lOBukgAUCYZPHFgAKCRAG+Q3lOBuk
gJhEAKCcU0DdXfnDOrES/dBxwCuFupA2JQCeLdV0PvWY0JicVOM5MQE0GqB4xzU=
=ae3R
-----END PGP SIGNATURE-----