# Source all dependencies from the following repositories in the specified order
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,50 @@
1
1
#
2
2
# ${project.version} release
3
3
#
4
-
r30: {
4
+
r31: {
5
5
title: ${project.name} ${project.version} released
6
6
id: ${project.version}
7
7
date: ${project.buildDate}
8
+
note: ''
9
+
When you have Gitblit installed as a service under Linux or Windows, you may need to edit your service script/definition. The command line to start Gitblit needs to be different, the classpath and class are speficied now.
10
+
11
+
See notes for release 1.9.0.
12
+
''
13
+
html: ~
14
+
text: ''
15
+
!! IMPORTANT BUG FIX FOR PASSWORD HASH UPGRADE !!
16
+
17
+
There is a severe bug in version 1.9.0, which can lock users out from their accounts.
18
+
When updating from a previous version to 1.9.0, existing stored passwords are rehashed
19
+
with a more secure password hash mechanism when a user first logs in after the update.
20
+
This happens when the password hashing mechanism was left at default and not specifically
21
+
set in the configuration. An error in the implementation will destroy the stored password
22
+
instead and the user can no longer log in.
23
+
24
+
Only certain circumstances will lead to this wrong behaviour. It will most likely
25
+
affect users of the Gitblit Docker container. If you did not encounter any problems,
26
+
update to 1.9.1 to be on the safe side. If you were hit by this bug, we are deeply sorry.
27
+
There is no way to fix the affected accounts other than to set a new password.
28
+
29
+
This is fixed in 1.9.1. Updates of existing installations should be made to 1.9.1, not 1.9.0.
- Fixed Linux service scripts to use `-cp` parameter instead of `-jar`.
35
+
changes: ~
36
+
additions: ~
37
+
dependencyChanges: ~
38
+
contributors: ~
39
+
}
40
+
41
+
#
42
+
# 1.9.0 release
43
+
#
44
+
r30: {
45
+
title: Gitblit 1.9.0 released
46
+
id: 1.9.0
47
+
date: 2020-02-01
8
48
note: ''
9
49
Gitblit uses Servlet 3.0 and thus drops support for Tomcat 6. Run on Tomcat 6 at your own risk.
10
50
@@ -18,7 +58,8 @@ r30: {
18
58
19
59
When the `realm.ldap.bindpattern` property is set, GitBlit will only bind as the user to LDAP, not to a manager account or anonymously.
20
60
21
-
Older password storage mechanisms are deprecated, PBKDF2 is the new default. When you switch from plaintext to a hashed scheme, or from the older hashed to the new PBKDF2 scheme, the stored password of a user will be rehashed with the more secure mechanism when the user logs in.
61
+
Older password storage mechanisms are deprecated, PBKDF2 is the new default. When you switch from plaintext to a hashed scheme, or from the older hashed to the new PBKDF2 scheme, the stored password of a user will be rehashed with the more secure mechanism when the user logs in.
62
+
!! THIS IS BROKEN IN 1.9.0. DO NOT UPDATE TO 1.9.0. USE 1.9.1 INSTEAD !!
22
63
''
23
64
html: ~
24
65
text: ''
@@ -1949,6 +1990,6 @@ r1: {
1949
1990
- James Moger
1950
1991
}
1951
1992
1952
-
snapshot: &r30
1953
-
release: &r29
1954
-
releases: &r[1..29]
1993
+
snapshot: &r31
1994
+
release: &r30
1995
+
releases: &r[1..30]
Original file line number
Diff line number
Diff line change
@@ -1,2 +1,2 @@
1
1
#!/bin/bash
2
-
java -cp gitblit.jar:ext/* com.gitblit.authority.GitblitAuthority --baseFolder data
2
+
java -cp "gitblit.jar:ext/*" com.gitblit.authority.GitblitAuthority --baseFolder data
@@ -8,7 +8,7 @@ Gitblit optionally allows a remote client to administer the Gitblit server. Thi
8
8
web.enableRpcManagement=false
9
9
web.enableRpcAdministration=false
10
10
11
-
**https** is strongly recommended because passwords are insecurely transmitted form your browser/rpc client using Basic authentication!
11
+
**https** is strongly recommended because passwords are insecurely transmitted from your browser/rpc client using Basic authentication!
12
12
13
13
The Gitblit JSON RPC mechanism, like the Gitblit JGit servlet, syndication/feed servlet, etc, supports request-based authentication. Making an *admin* request will trigger Gitblit's basic authentication mechanism. Listing of repositories, generally, will not trigger this authentication mechanism unless *web.authenticateViewPages=true*. That means its possible to allow anonymous enumeration of repositories that are not *view restricted* or *clone restricted*. Of course, if credentials are provided then all private repositories that are available to the user account will be enumerated in the JSON response.
14
14
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Open `data/gitblit.properties` in your favorite text editor and make sure to rev
17
17
**NOTE:** You can only have **one** SSL certificate specified for a port.
18
18
4. exit the authority app
19
19
4. Windows: Execute `gitblit.cmd` or `java -cp gitblit.jar;"%CD%\ext\*" com.gitblit.GitBlitServer --baseFolder data` from a command-line
20
-
Linux/OSX: Execute `gitblit.sh` or `java -cp gitblit.jar;ext/* com.gitblit.GitBlitServer --baseFolder data` from a command-line
20
+
Linux/OSX: Execute `gitblit.sh` or `java -cp "gitblit.jar:ext/*"" com.gitblit.GitBlitServer --baseFolder data` from a command-line
21
21
5. Open your browser to <http://localhost:8080> or <https://localhost:8443> depending on your chosen configuration.
22
22
6. Enter the default administrator credentials: **admin / admin** and click the *Login* button
23
23
**NOTE:** Make sure to change the administrator username and/or password!!
0 commit comments