|
5 | 5 | title: ${project.name} ${project.version} released
|
6 | 6 | id: ${project.version}
|
7 | 7 | 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 | + '' |
9 | 13 | 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 | + '' |
11 | 31 | 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`. |
13 | 35 | changes: ~
|
14 | 36 | additions: ~
|
15 | 37 | dependencyChanges: ~
|
|
36 | 58 |
|
37 | 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.
|
38 | 60 |
|
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 !! |
40 | 63 | ''
|
41 | 64 | html: ~
|
42 | 65 | text: ''
|
|
0 commit comments