Skip to main content
Jump to: navigation, search

Difference between revisions of "EGit/New and Noteworthy/5.3"

m (GPG-signing Commits)
(GPG-signing Commits)
Line 7: Line 7:
 
[[File:egit-commit-sign.png]]
 
[[File:egit-commit-sign.png]]
  
The new icon in the upper right will allow you to toggle commit signing. The default is read from the Git configuration. If the config option <code>commit.gpgsign</code> is set to <code>true</code>, the button will be selected by default. The value of <code>user.signingkey</code> will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. Keys will be looked up from <code>~/.gnupg/pubring.kbx</code> (GPG's keybox file).
+
The new icon in the upper right will allow you to toggle commit signing on or off. The default is read from the Git configuration. If the config option <code>commit.gpgsign</code> is set to <code>true</code>, the button will be selected by default. The value of <code>user.signingkey</code> will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. If no key can be found a commit will fail.
 +
 
 +
Keys will be looked up from your GPG keyring (either <code>~/.gnupg/pubring.kbx</code> or <code>~/.gnupg/secring.gpgx</code>).  
 +
 
 +
See the following GitHub help pages for help on GPG signing keys:
 +
* [https://help.github.com/articles/generating-a-new-gpg-key/ Generating a new GPG key]
 +
* [https://help.github.com/articles/telling-git-about-your-signing-key/ Telling Git about your signing key]
 +
* [https://help.github.com/articles/associating-an-email-with-your-gpg-key/ Associating an email with your GPG key]
  
 
== SSH Library ==
 
== SSH Library ==

Revision as of 11:25, 18 January 2019

EGit

GPG-signing Commits

EGit 5.3.0 can sign commits with GPG.

Egit-commit-sign.png

The new icon in the upper right will allow you to toggle commit signing on or off. The default is read from the Git configuration. If the config option commit.gpgsign is set to true, the button will be selected by default. The value of user.signingkey will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. If no key can be found a commit will fail.

Keys will be looked up from your GPG keyring (either ~/.gnupg/pubring.kbx or ~/.gnupg/secring.gpgx).

See the following GitHub help pages for help on GPG signing keys:

SSH Library

In the last release we had introduced a new SSH client based on the Apache MINA sshd library as an alternative to the JSch-based client. In EGit 5.3.0 the default settings are switched: by default, the Apache MINA implementation is used.

TBD: With Egit 5.3.0 it is now also possible to use encrypted new-style OpenSSH private keys, for instance password-protected ed25519 keys.

On Java versions older than 8u161, you may need to download and install the "JCE Unlimited Strength Jurisdiction Policy Files" for this to work. OpenSSH uses the AES encryption with 256bit keys, which is available in older Java only with this extension. On newer Java versions, "unlimited strength" encryption is enabled by default, so you need not do anything.

We plan to remove the old JSch SSH implementation completely in a future release of EGit.

TBD: Merge and compare editor improvements

The merge and compare viewers have been improved to enable more functions (such as "Show Whitespace") also in edge cases where they didn't work before, and to react on changes done outside of the merge or compare editor.

Other Changes

The complete list of new features and bug fixes is available in the release notes.

Contributors

The following X developers worked on this release:

<TBD: list of contributors, number>

Back to the top