Home → Stable →

GPG Keychain: Spacing bug with fingerprint

• Edit

jackiam2003

21 Oct, 2016 07:37 AM

When I View the fingerprint Of a item there is a extra space in the middle of the fingerprint making it hard to compare to fingerprints online.
example.
Original from GPG keychain.
E4AC D397 5427 A5BA 8450 A1BE B01C 8B00 6DA7 7FAA
^ | There are two spaces right there

Expected
There should only be a single space and fingerprint so that you can compare it to fingerprints online without having to edit out the space.

macOS           10.12       16A323
GPG Suite       2016.10     21  
GPGMail -
GPG Keychain    1.3.2       1245
GPGServices     1.11        916 
MacGPG2         2.0.30      884 
GPGPreferences  2.0.1       902 
Libmacgpg       0.7         775 
pinentry        0.9.7       4

• 2016-10-21_07-37_DebugInfo.gpg 16.4 KB

1. Support Staff 1 Posted by Steve on 21 Oct, 2016 12:39 PM

   

   Hey jacki,

   This KB-article gives an overview over all shortcuts.

   Note this line:

   ⇧⌘C Copy fingerprint without spaces (also works with x keys selected)

   The double space in the middle of the fingerprint is intentional to actually make it easier to get a visual orientation for all those 4 digit packages of the fingerprint.

   There is also a problem with the way we currently shorten the fingerprint in the side tab that opens after double clicking a key.

   We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.

   All the best,
   steve

   • Edit

2. Support Staff 2 Posted by Steve on 31 Oct, 2016 09:39 AM

   

   Hi Jacki,

   this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.

   Should the problem persist, please re-open this discussion and let us know. For more questions that are not related to this specific problem, you are welcome to create a new discussion any time.

   Best, steve

   Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.

   • Edit

3. Steve closed this discussion on 31 Oct, 2016 09:39 AM.