Skip to content

Commit 34e77dd

Browse files
committed
📖docs: Add update of service scripts in upgrade GO documentation
Also: release notes.
1 parent 12dea00 commit 34e77dd

File tree

2 files changed

+49
-4
lines changed

2 files changed

+49
-4
lines changed

‎releases.moxie

+27-4
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,33 @@ r31: {
55
title: ${project.name} ${project.version} released
66
id: ${project.version}
77
date: ${project.buildDate}
8-
note: ~
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+
''
913
html: ~
10-
text: ~
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.
30+
''
1131
security: ~
12-
fixes: ~
32+
fixes:
33+
- Fixed broken password hash upgrade destroying existing stored passwords on update.
34+
- Fixed Linux service scripts to use `-cp` parameter instead of `-jar`.
1335
changes: ~
1436
additions: ~
1537
dependencyChanges: ~
@@ -36,7 +58,8 @@ r30: {
3658

3759
When the `realm.ldap.bindpattern` property is set, GitBlit will only bind as the user to LDAP, not to a manager account or anonymously.
3860

39-
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 !!
4063
''
4164
html: ~
4265
text: ''

‎src/site/upgrade_go.mkd

+22
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,25 @@
1+
## Upgrading Gitblit GO (1.9.1+)
2+
3+
The command line to start Gitblit has changed from
4+
5+
```
6+
java -jar gitblit.jar --baseFolder data
7+
```
8+
9+
to
10+
11+
```
12+
java -cp "gitblit.jar:ext/*" com.gitblit.GitBlitServer --baseFolder data
13+
```
14+
15+
or on Windows to
16+
17+
```
18+
java -cp gitblit.jar;"%CD%\ext\*" com.gitblit.GitBlitServer --baseFolder data
19+
```
20+
21+
The class path and main class need to be specified now. If you have installed Gitblit as a service you will need to adjust the service scripts or definitions accordingly.
22+
123
## Upgrading Gitblit GO (1.7.0+)
224

325
The default `gitblit.properties` file has been split into two files: `gitblit.properties`, which is the recommended file for setting your configuration, and `defaults.properties` which are Gitblit's default settings.

0 commit comments

Comments
 (0)