I still need some guidance please as there appear to be contradictions or different information for the same keyring contents.
Using GNU Privacy Assistant there are two keys shown with my relevant main email address with details as follows:
The first, dated 2019-06-22 has a Key ID:2B24B97C, a fingerprint starting E9F0… is shown as fully valid and can be used for certification, signing and encryption.
The second, dated 2019-07-05 has a Key ID:68EC645D, a fingerprint starting 1EAD… is shown with unknown validity and not available for encryption.
Neither are shown as disabled.
Using Enigmail Key Management there are still two keys shown with my relevant email address with details as follows:
The first, dated 22/06/19 has a Key ID:BB7E69A42B24B97C, a fingerprint starting E9F0… is shown with key validity “disabled” but with ultimate owners trust.
The second, dated 05/07/19 has a Key ID:50A3AF5F68EC645D, a fingerprint starting 1EAD… is shown with unknown validity or trust.
Although the presentation is different it is clear these keys are the same in both applications so why are the Key IDs different and note that Enigmail App shows the 22/06/19 dated key as disabled?
When I use console to look at the keys with a view to creating another subkey for use in authentication I have as follows:-
alastair@AJBR-W530:~> gpg --edit-key --expert ajbudge@errichel.co.uk
gpg (GnuPG) 2.2.17; Copyright (C) 2019 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
sec rsa2048/BB7E69A42B24B97C
created: 2019-06-22 expires: 2020-06-21 usage: SC
trust: ultimate validity: ultimate
*** This key has been disabled
ssb rsa2048/50CBBAAAC6A53584
created: 2019-06-22 expires: 2020-06-21 usage: E
[ultimate] (1). ajbudge@errichel.co.uk <ajbudge@errichel.co.uk>
gpg>
This shows the disabled key but not the other although both have the same email address.
Please could somebody reassure me that all is well and explain what I have yet to do to get the key dated 05/07/19 which has not been disabled, to show as available for encryption and enable creation of authentication subkey.