Skip to content

Update GPG key generation instructions (for older Git for Windows versions)#366

Merged
stefaniuk merged 1 commit intomainfrom
chrisbloe-patch-1
Feb 5, 2026
Merged

Update GPG key generation instructions (for older Git for Windows versions)#366
stefaniuk merged 1 commit intomainfrom
chrisbloe-patch-1

Conversation

@chrisbloe
Copy link
Contributor

Clarified the option for ECC key generation and added a note about Git for Windows versions.

…sions)

Clarified the option for ECC key generation and added a note about Git for Windows versions.
@chrisbloe chrisbloe requested a review from a team as a code owner February 5, 2026 10:46
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 5, 2026

Copy link
Contributor

@stefaniuk stefaniuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@stefaniuk stefaniuk added this pull request to the merge queue Feb 5, 2026
Merged via the queue into main with commit 63f7a81 Feb 5, 2026
3 checks passed
@stefaniuk stefaniuk deleted the chrisbloe-patch-1 branch February 5, 2026 14:00
```

1. Pick `ECC (sign and encrypt)` then `Curve 25519` ([Ed25519](https://en.wikipedia.org/wiki/EdDSA#Ed25519) offers the strongest encryption at time of writing)
1. Pick `(9) ECC (sign and encrypt)` then `Curve 25519` ([Ed25519](https://en.wikipedia.org/wiki/EdDSA#Ed25519) offers the strongest encryption at time of writing)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Option 9 actually states (9) ECC and ECC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants