Change Details

When importing a single secret key, you are asked if this is your own key, to decide if the owner trust is set to ultimate or not. This question may confuse people if they import a shared key (which is done for reading encrypted mail to functional mail addresses). If people answer "No", as they should, they may wonder what to do with this certificate in order to use it, as it is now marked "not certified". The answer would be that they need to certify it with their own key. To lead the user to the solution we could open a certification window next, as we do when importing a single public key (if the person has their own secret key, that is).

When importing a single secret key, you are asked if this is your own key, to decide if the owner trust is set to ultimate or not. This question may confuse people if they import a shared key (which is done for reading encrypted mail to functional mail addresses). If people answer "No", as they should, they may wonder what to do with this certificate in order to use it, as it is now marked "not certified". The answer would be that they need to certify it with their own key. **Edit 2025-02-12:** To lead the user to the solution we should: - Either add an explanation text directly above the buttons - Or change the question to: "Are you the exclusive user of this secret key?" (which should be self explanatory) In any case choosing "No" should result in opening a certification window, if the person has their own secret key. Otherwise do not open a certification window, i.e. do nothing. Other thoughts: We do not need several versions of an explanation text because: - The case "user has no own secret key" can be ignored as it is obvious that you can not certify a key if you do not have an other key to do it. (And people tend to create one anyway if they see an empty keyring with the "Create keypair" button.) - In case the import is of an updated secret (sub)key, which was already certified by the users own personal key we need not open the "is this your own key" window at all.

When importing a single secret key, you are asked if this is your own key, to decide if the owner trust is set to ultimate or not. This question may confuse people if they import a shared key (which is done for reading encrypted mail to functional mail addresses). If people answer "No", as they should, they may wonder what to do with this certificate in order to use it, as it is now marked "not certified". The answer would be that they need to certify it with their own key. **Edit 2025-02-12:** To lead the user to the solution we could open a certification window next,should: - Either add an explanation text directly above the buttons - Or change the question to: "Are you the exclusive user of this secret key?" (which should be self explanatory) In any case choosing "No" should result in opening a certification window, if the person has their own secret key. Otherwise do not open a certification window, i.e. do nothing. Other thoughts: We do not need several versions of an explanation text because: - The case "user has no own secret key" can be ignored as it is obvious that you can not certify a key if you do not have an other key to do it. as we do when importing a single public key (if the person has their own secret (And people tend to create one anyway if they see an empty keyring with the "Create keypair" button.) - In case the import is of an updated secret (sub)key, that is).which was already certified by the users own personal key we need not open the "is this your own key" window at all.