Page MenuHome GnuPG

`--expert --full-generate-key` | Inconsistencies regarding capabilities presented for selection
Closed, InvalidPublic

Description

Hello. It will be noted at the beginning of the output resulting from the command below, whatever the option selected making possible the selection of capacities among a set of capacities, that for each type of key selected, the actions said to be possible and those said to be authorized are announced.

Illustration; output filtered:

# gpg --expert --full-generate-key
Please select what kind of key you want:
 (11) ECC (set your own capabilities)
Your selection? 11
Possible actions for this ECC key: Sign Certify Authenticate 
Current allowed actions: Sign Certify 
 (S) Toggle the sign capability
 (A) Toggle the authenticate capability
 (Q) Finished

It will then be unambiguously understood:

  • by 'Possible actions', the explicit meaning of actions technically achievable, therefore supported by the OpenPGP standard.
  • by 'Current allowed actions', the implicit meaning of currently achievable capabilities.
  • options presented for selection directly after the line 'Current allowed actions: <capabilities>' are representative of the currently achievable capabilities.

It will be observed the following inconsistencies:

  • 'Certify', which is a representative of a currently achievable capability, is however not presented for selection. The '(C) Toggle the certify capability' option is missing isn't it?
  • The '(A) Toggle the authenticate capability' option, which is presented for selection, is however not a representative of a currently achievable capability.

What could have led to this state?

Event Timeline

werner added a subscriber: werner.

Please use the mailing list for such questions.

Wouldn't anyone suspect that you are in the habit of dispensing the ''Invalid'' label without discernment for reports that, however, have no basis as such? But what on earth could you possibly be trying to achieve by acting in this way?

I asked you to write to the mailing list instead of filing a bug report. A mailing list has a far wider audience than a single bug report. Our bug tracker is not a help forum or a place to ask questions.

We will therefore have to form an idea of ​​the kind of person one must be, to be able to deliberately put oneself in a position of not being able to answer, by using a rather dubious pretext, insinuating the ignorance of a third audience about the inconsistency which, however, anyone could independently state. Thus, in this path you have chosen to persevere. Well then, you alone know the rules of your game.