Feb 13th, 2017

For number of reasons, I've set up a new GPG key and will be transitioning to it
as my key.

The old key will be valid for sometime, but I'd prefer if you switch to the new
key for future communications.

Also, if you feel like, please consider signing the key. This document is signed
with both keys for verification.

Old key was:

rsa2048/0xD4E55B033CF4F87F 2014-03-20 [SC] [expires: 2017-03-22]
      Key fingerprint = C9F8 AA93 C29F 0716 7E75  74EC D4E5 5B03 3CF4 F87F

The new key is:
rsa4096/0xED5426FAEC7901DD 2017-02-08 [SC] [expires: 2022-02-07]
      Key fingerprint = 4970 CC92 010A 4087 67C6  9904 ED54 26FA EC79 01DD

You can fetch my key from sks-keyservers.net keyserver.

gpg --keyserver hkp://pool.sks-keyservers.net/ --recv-keys 0xED5426FAEC7901DD

If you already know my old key, you can now verify that the new key is
signed by the old one:

  gpg --check-sigs 0xED5426FAEC7901DD

If you don't already know my old key, or you just want to be double
extra paranoid, you can check the fingerprint against the one above:

  gpg --fingerprint 0xED5426FAEC7901DD

If you are satisfied that you've got the right key, and the UIDs match
what you expect, I'd appreciate it if you would sign my key:

  gpg --sign-key 0xED5426FAEC7901DD

Lastly, if you could upload these signatures, i would appreciate it.
You can either send me an e-mail with the new signatures (if you have
a functional MTA on your system):

  gpg --armor --export 0xED5426FAEC7901DD | mail -s 'OpenPGP Signatures' mail@dbalan.in

Or you can just upload the signatures to a public keyserver directly:

  gpg --keyserver hkp://pool.sks-keyservers.net --send-key 0xED5426FAEC7901DD

Please let me know if there is any trouble, and sorry for the
inconvenience.

Regards,

dbalan
