Update contact/uncertify.sh

[diveshuttam]

pgpg/src/cmd/contact/uncertify.sh

Line 12 in d108baf

echo "Try the command: $(basename $0) gpg --key-edit $@"

[diveshuttam]

@dashohoxha this as of now just prints the instructions for the user and as such nothing needs to be done.
Also I am not able to find an easy way to achieve this in gpgme we but to use the same interact way. Since it is avoided here I wanted to know if it needs to be done in gpgme.

BTW this is one of the things we may do to remove interact functionality alltogether from gpgme. Though personally I don't we should do this as it creates burden on the user.

Also one more thing, I think that the message should be modified to egpg gpg --edit-key "$@" as egpg and gpg contexts(homedir) may be different.

[dashohoxha]

Also one more thing, I think that the message should be modified to egpg gpg --edit-key "$@" as egpg and gpg contexts(homedir) may be different.

You are right. But $(basename $0) evaluates to egpg.

Also I am not able to find an easy way to achieve this in gpgme we but to use the same interact way. Since it is avoided here I wanted to know if it needs to be done in gpgme.

You can give it a try with the interactive key editing. I am not sure why I have not implemented it. Maybe it was too difficult, or maybe I thought it is not frequently used and not so important. But you can give it a try.

[dashohoxha]

BTW this is one of the things we may do to remove interact functionality alltogether from gpgme. Though personally I don't we should do this as it creates burden on the user.

I did not get what do you mean here.

[diveshuttam]

I did not get what do you mean here.

As you commented earlier that using interactive is not that good.
The strategy used here (tell the user what to do) can be one of the points to discuss while we discuss about this on gnupg-devel.
I personally don't think it is good but just keeping all the options and evaluating them is good.

[dashohoxha]

Oh, I see.

The aim of egpg has never been to replace gpg, but to make it easier for the users.
One of the design goals of egpg is that it tries to integrate seamlessly with gpg, so that the users can switch to gpg easily if they find that the assumptions and the simplified interface of egpg restricts them somehow. One of the ways to achieve this goal is by implementing the command egpg gpg ..... Also, in the case of egpg contact uncertify, by telling them what to do we also show them and make them realize that actually they can use all the commands of gpg within egpg.

Of course, some things that can be done with gpg can break the assumptions of egpg, for example creating more than one secret key on the same keyring. In this case egpg will continue using the first one that is listed. If a user does this, probably he knows what he is doing and can continue using gpg directly, instead of using egpg.