Hi,

I am trying to add a new GPG key that I use to sign my commits, the UI does not accept it, says: `No public keys suitable for encryption found. ` .. which is correct, as this is a key with only a signing subkey. I do not encrypt anything with the key, only sign commits.

Note:
- There is an older key with the same associated email that is about to expire. I keep it to verify older commits, just in case, but I read in other posts this can be an issue?
- That key is also for signing only (at least I think it is), so not sure why it worked before and not anymore?

I understand I cannot use this key to encrypt emails, this is intended (because the associated email is only for signing, not communicating). But why not allow the upload of the key?


Best Regards,
Guillermo

You sign your commits on your local machine before you push, so there’s no reason to upload a private key to sr.ht (nor should you generally be uploading private keys anywhere)

> On Feb 21, 2024, at 3:23 AM, Guillermo Marcus <gmarcus@gmarcus.net> wrote:
> 
> Hi,
> 
> I am trying to add a new GPG key that I use to sign my commits, the UI does not accept it, says: `No public keys suitable for encryption found. ` .. which is correct, as this is a key with only a signing subkey. I do not encrypt anything with the key, only sign commits.
> 
> Note:
> - There is an older key with the same associated email that is about to expire. I keep it to verify older commits, just in case, but I read in other posts this can be an issue?
> - That key is also for signing only (at least I think it is), so not sure why it worked before and not anymore?
> 
> I understand I cannot use this key to encrypt emails, this is intended (because the associated email is only for signing, not communicating). But why not allow the upload of the key?
> 
> 
> Best Regards,
> Guillermo

Please accept my apologies for misunderstanding your original question. Of course you know not to upload private keys.

> On Feb 21, 2024, at 7:42 PM, Adam King <Adam@thekings.ca> wrote:
> 
> You sign your commits on your local machine before you push, so there’s no reason to upload a private key to sr.ht (nor should you generally be uploading private keys anywhere)
> 
>> On Feb 21, 2024, at 3:23 AM, Guillermo Marcus <gmarcus@gmarcus.net> wrote:
>> 
>> Hi,
>> 
>> I am trying to add a new GPG key that I use to sign my commits, the UI does not accept it, says: `No public keys suitable for encryption found. ` .. which is correct, as this is a key with only a signing subkey. I do not encrypt anything with the key, only sign commits.
>> 
>> Note:
>> - There is an older key with the same associated email that is about to expire. I keep it to verify older commits, just in case, but I read in other posts this can be an issue?
>> - That key is also for signing only (at least I think it is), so not sure why it worked before and not anymore?
>> 
>> I understand I cannot use this key to encrypt emails, this is intended (because the associated email is only for signing, not communicating). But why not allow the upload of the key?
>> 
>> 
>> Best Regards,
>> Guillermo