|
1 | | -Release song: https://www.youtube.com/watch?v=kymdKYtkJbQ |
| 1 | +Release song: https://www.youtube.com/watch?v=6tpGC4lgpMg |
2 | 2 |
|
3 | | -Passbolt 5.4.0 ships with encrypted metadata and the accompanying new resource types promoted to stable. These capabilities have been battle-tested for months, and the most remaining edge cases have been smoothed out so they can now be enabled for everyone. |
| 3 | +This hot-fix addresses several issues introduced in recent v5.x releases. |
4 | 4 |
|
5 | | -Removing the beta label means that every new instance starts with encrypted metadata activated by default. As a result, features introduced in previous releases, such as icons, multiple URIs and custom fields, are available from day one without any action from end-users. |
| 5 | +Since v5.3, organizations running Passbolt on servers with a locale different from en-UK could encounter issues to update or later to use the application, which have now been resolved. |
6 | 6 |
|
7 | | -For existing instances, the activation process has been simplified: administrators can decide with a single click whether their organisation is ready or would prefer to postpone the launch. Once enabled, the instance immediately supports the new resource types and their extended capabilities. |
| 7 | +It also fixes a problem where organizations that had manually disabled encrypted metadata using the kill switch available to system administrators were unable to initiate imports |
| 8 | +credentials from the web application. This was a side effect of recent work preparing for the upcoming zero-knowledge capability, which will further strengthen the encrypted |
| 9 | +metadata feature introduced earlier. |
8 | 10 |
|
9 | | -Because the change may disrupt external integrations, existing content is not migrated automatically, migration remains the responsibility of content owners or administrators. It can be performed item-by-item by users in the main workspace or organisation-wide with the resource-metadata administration migration tool. |
| 11 | +Finally, since v5.0, resources whose secrets had been modified, irrespective of whether the secret was a password, a TOTP, or a secure note, have had their expiration dates |
| 12 | +automatically rotated, which was not the expected behaviour. The expected behaviour is now restored: the expiration date is rotated only when the password is edited. |
10 | 13 |
|
11 | | -Revisiting resource capabilities was also an opportunity to increase the maximum size of secret notes to 50 000 characters, leaving ample room for full certificate chains, keys of any flavour or any long text you need to keep encrypted. |
12 | | - |
13 | | -This release further improves cryptographic performance by introducing elliptic-curve keys (Curve25519/Ed25519) for new users. These keys provide security comparable to RSA-3072 while significantly reducing processing time and payload size. |
14 | | - |
15 | | -Performance has been tuned for large organisations that manage substantial numbers of users or resources. Among other improvements: Users' workspace now opens more quickly, and deleting multiple resources generates fewer I/O operations. |
16 | | - |
17 | | -Czech joins the list of supported languages, allowing native speakers to use Passbolt entirely in their own words, vítejte! |
18 | | - |
19 | | -Many thanks to everyone who reported issues and tested encrypted metadata over the past months. Your feedback made this release possible and brings these new features to all users today. |
20 | | - |
21 | | -## [5.4.0] - 2025-08-12 |
22 | | -### Added |
23 | | -- PB-43713 Translate the application in Czech |
24 | | -- PB-44285 Add endpoint to help clients enable E2EE by default for new instances |
25 | | -- PB-44184 As an administrator I should not be allowed to retrieve resources to migrate from v4 to v5 resource types from v4 resource types that are deleted |
26 | | -- PB-44071 Add a cleanup tasks to soft-delete inactive users with same usernames |
27 | | -- PB-44376 Set ECC key type as a default for new users |
28 | | -- PB-44405 Add new healthcheck to notify administrators when there are no active metadata key if E2EE is enabled |
29 | | -- PB-44406 Add new healthcheck to notify administrators when zero-knowledge disabled and the server does not have access to the shared metadata key |
30 | | -- PB-44407 Add new healthcheck to notify administrators when server cannot validate its own shared metadata private key |
31 | | -- PB-44416 Add metadata settings getting started endpoint |
32 | | -- PB-38155 Add JSON schema definition to resource types migrations |
33 | | -- PB-44474 Switch encrypted metadata plugin to stable |
34 | | -- PB-43631 As an admin running a command as root, I should see the name of the command in the suggestion proposed by the CLI |
| 14 | +We thank the community for promptly reporting these issues. |
35 | 15 |
|
| 16 | +## [5.4.1] - 2025-08-13 |
36 | 17 | ### Fixed |
37 | | -- PB-43187 Retrieve user last logged data from users table instead of the log to improve application performance |
38 | | -- PB-43922 Fix notification emails about a resource update |
39 | | -- PB-43709 Fix enabling E2EE without a key should trigger an error |
40 | | -- PB-44093 Fix a warning message in ActionLogsUsernameQueryStrategy |
41 | | -- PB-44177 Fix as a user I should not be allowed to create v4 resource if the resource type is deleted |
42 | | -- PB-44179 Fix as user I should not view/index v4 resource types if the resource type is deleted |
43 | | -- PB-43936 Fix IsValidEncryptedMetadataPrivateKey should log, then return false and not throw an exception if isMessageForRecipient fails |
44 | | -- PB-44182 Fix as user I should not be allowed to delete a v4 resource if v4 resource type is deleted |
45 | | -- PB-44181 Fix as user I should not be allowed to share a v4 resource if v4 resource type is deleted |
46 | | -- PB-44252 Fix as an admin I should not be able to set the role of a user to guest |
47 | | -- PB-44178 Fix as a user I should not be allowed to update v4 resource if the resource type is deleted |
48 | | -- PB-44180 Fix as user I should not view/index v5 resource types if the resource type is deleted |
49 | | -- PB-44186 Fix as an administrator I should not be able to rotate the metadata key for resources that have a deleted resource types |
50 | | -- PB-44189 Fix command line metadata commands should be loaded in debug mode only |
51 | | -- PB-43936 Fix isMessageForRecipient should work if encryption is done with main key |
52 | | -- PB-41818 Fix as a user setting a date as boolean the API should not return a 500 code response |
53 | | - |
54 | | -### Maintenance |
55 | | -- PB-43524 Create a TestData plugin in plugins/PassboltCe |
56 | | -- PB-44087 Remove V331 backward compatibility migration |
57 | | -- PB-44267 Bump SeleniumApi plugin version |
58 | | -- PB-43752 Add assertJson assertions to folders endpoints |
59 | | -- PB-41818 Bump cakephp version to 5.2.6 |
| 18 | +- PB-44220 Enforces the format to datetime string when persisting the last_logged_in field on users login |
0 commit comments