From 040091508e69df76b1504d10089444e8d6bae2ab Mon Sep 17 00:00:00 2001 From: James Moger <james.moger@gmail.com> Date: Sun, 17 Jan 2016 17:31:14 -0500 Subject: [PATCH] Merge pull request #1004 from RedShift1/ticket-#998-document-DH-keysize --- src/site/setup_transport_http.mkd | 12 +++++++++++- 1 files changed, 11 insertions(+), 1 deletions(-) diff --git a/src/site/setup_transport_http.mkd b/src/site/setup_transport_http.mkd index fd611d4..4de7596 100644 --- a/src/site/setup_transport_http.mkd +++ b/src/site/setup_transport_http.mkd @@ -5,7 +5,7 @@ You must tell Git/JGit not to verify the self-signed certificate in order to perform any remote Git operations. **NOTE:** -The default self-signed certificate generated by Gitlbit GO is bound to *localhost*. +The default self-signed certificate generated by Gitblit GO is bound to *localhost*. If you are using Eclipse/EGit/JGit clients, you will have to generate your own certificate that specifies the exact hostname used in your clone/push url. You must do this because Eclipse/EGit/JGit (< 3.0) always verifies certificate hostnames, regardless of the *http.sslVerify=false* client-side setting. @@ -17,6 +17,16 @@ - **Command-line Git** ([Git-Config Manual Page](http://www.kernel.org/pub/software/scm/git/docs/git-config.html)) <pre>git config --global --bool --add http.sslVerify false</pre> +**NOTE:** +When generating self-signed certificates, the default Java TLS settings will be used. These default settings will generate a weak Diffie-Hellman key. +#### Java 8 +The default is a 1024 bit DH key. +You can up the number of bits used by appending the following command line parameter when starting Gitblit: +<pre>-Djdk.tls.ephemeralDHKeySize=2048</pre> +2048 bits is the maximum (Java limitation), and is still considered secure as of this writing. +#### Java 7 +The default is a 768 bit key. <b>This is hardcoded in Java 7 and cannot be changed.</b>. It is very weak. If you require longer DH keys, use Java 8. + ### Http Post Buffer Size You may find the default post buffer of your git client is too small to push large deltas to Gitblit. Sometimes this can be observed on your client as *hanging* during a push. Other times it can be observed by git erroring out with a message like: error: RPC failed; result=52, HTTP code = 0. -- Gitblit v1.9.1