Comments and changes to this ticket
-
Alex (via GPGTools) February 21st, 2011 @ 01:20 AM
- State changed from new to open
- Milestone set to 0.8.13
- Assigned user set to Mento
- Importance changed from High to
-
-
Mento February 21st, 2011 @ 11:46 AM
- State changed from open to resolved
-
Axel February 21st, 2011 @ 05:14 PM
Works as designed?
This means in order to see my own public key I cannot use GPGKeychain.
I have to use the command line "gpg2 --list-keys" which properly
displays my public key infos?It is somehow misleading that I have to export my "sec" key
to get the "pub" key of my own.Regards, Axel.
-
Mento February 21st, 2011 @ 09:55 PM
The secret and the public key are a key pair. In the GPG Keychain Access you see this key pair.
Why should you only want to see the public?pub = Public key only.
sec = Public and secret key. -
Axel February 22nd, 2011 @ 08:38 AM
I want to see both!
That is exactly my problem because in the current version
I just see the secret key listed.Regards, Axel.
-
Alex (via GPGTools) February 22nd, 2011 @ 09:13 AM
Hi Axel, maybe there is a "communication issue" between Mento and you ;) Maybe you could write what you would like to see in this form:
- Workflow:
1.1. Step 1
1.2. Step 2 - Expected:
2.1. To see XYZ - Instead:
3.1. I see ZYX
Currently the only difference I can see is that my secret key is bold and the type is called "sec" instead of "pub". But all the relevant information are shown.
- Workflow:
-
Axel February 22nd, 2011 @ 09:52 AM
-
Workflow
I open GPGKeychain and see my own key entry in bold with type "sec". -
Expectation
I expected to see my own key as type "pub" and after opening the
tree I would see the "sec" part as well
or
I see the "sec" part and after clicking the triangle I would see
my "pub" key too. - Instead
I can only see the "sec" part which I assume to be the secret key only.
I do not dare to export the "sec" key because I don't want my secret
key ever exported. Instead after starting an export I see a deselected
checkbox which prevents secret key export.
My own public key is not explicitly listed.
Hope this makes things clear now.
Of course it is your design decision. Normal users might be misguided by
the current implementation IMHO.Cheers, Axel.
-
-
Mento February 22nd, 2011 @ 10:36 AM
Why do you want to see the public and the secret key?
This makes, in my opinion, no sense. -
Alex (via GPGTools) February 22nd, 2011 @ 11:30 AM
- State changed from resolved to hold
This makes, in my opinion, no sense.
@Mento: It doesn't make any sense because the information are the same? So "sec" only means that you have the secret key, too?
I can only see the "sec" part which I assume to be the secret key only.
@Axel: I think this assumption is not correct.
My own public key is not explicitly listed.
Would it make sense to write "sec+pub" instead of only "sec"?
-
Mento February 22nd, 2011 @ 11:50 AM
Yes and yes.
"sec+pub" would make sense, except that the column is too narrow.
-
Alex (via GPGTools) February 22nd, 2011 @ 11:54 AM
Then maybe:
- pub (usually)
- sec (is there a case were you only have the secret key?)
- both (your own key)
-
-
steve February 22nd, 2011 @ 12:46 PM
- State changed from hold to resolved
Fixed in 0.8.4b.
Double click any key in your list to get to the key-inspector. There you'll now find the info "Public key" or "Secret and public key".
Kudos to Mento!
-
steve June 18th, 2015 @ 12:59 PM
- State changed from resolved to released
- Importance cleared.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป