Can't create a 25519 key for encryption

[NearestWater262]

In Kleopatra, it will let me create a 25519 key for use in Encryption, but in GPGF this option during key creation is greyed out. Why is this?

[saturneric]

The difference lies in the design philosophy of Kleopatra and GpgFrontend. In Kleopatra, key generation typically creates both a primary key and a subkey automatically. The primary key is often Ed25519 for signing, and the subkey is Cv25519 for encryption. This approach simplifies the process for users who prefer an automated setup.

In contrast, GpgFrontend is designed to give users full control over their key structure. It allows them to explicitly choose the algorithm for both the primary key and any subkeys, without enforcing defaults or automatically generating subkeys. This means users can create a primary key of any supported type, such as Ed25519, and then manually add subkeys as needed.

[NearestWater262]

Thank you very much for this explanation. Now I will know what to do.

However I think for an average user, this would simply present frustration. Can you please make a shortcut like Kleopatra does? Mostly people using GPG will be making keys so they can perform encryption. I think rarely would someone would not want to have this.

Perhaps you can have a checkbox that is checked (or unchecked) by default that says something like "Create subkey for encryption?"

[saturneric]

I understand your concern, and I agree that for most users, creating keys should be a smooth and straightforward experience. I’m planning to add a simplified wizard, similar to Kleopatra, to provide convenient key generation options for common primary and subkey combinations. This should make it easier for users to quickly generate keys without having to configure every detail manually.