New features: Access links (sharing) for packages. Access to a package can now be granted using a unique access link. Details: Any number of access links to a package can be created, and they can be created by the sender/author of the package (if allowed by the administrator, see Settings - Configuration - Packages - General - Users can share packages) or by an administrator. A link can also be created for a specific subfolder within a package, where the link grants access only to the contents of this folder and not to the entire package. For links, it is possible to set: access permissions (read-only, upload-only, read+write), expiration, password, limitation on the number of accesses, and accessibility (public, internal, private). This makes it possible, for example, to share a package (or only its folder) for edits as well, using a password-protected unique link, with a third party that does not need to have an account in the application - an access link is sufficient. This is done via the “Share folder” button in the package detail. Packages that were shared with the user via an access link are visible to the signed-in user in a new menu “Shared with me”. It works similarly to (and may in the future replace) the feature of cooperative packages and contributors.
Adding the “Audit Log” feature to a package for users (senders and contributors). Suitable especially for cooperative packages, or packages with the new access links. It allows the sender and contributors, if enabled by the administrator, to view who and what was last done with the package (uploading files, moving, deleting, downloading, etc.). Using permissions, the administrator can define whether: the user does not see the package audit log at all (original state) sees the basic one (with basic events: work with files and links - suitable for regular users) or sees the extended one (with all package events, including scans, encryption, etc. - for advanced users or administrators' users)
Policies and configuration profiles, which allow the administrator to set different configuration for different users, groups, or IP addresses and ranges. Specifically: Profiles for detection engines - in Detection settings, for individual detection engines it is possible to create several different profiles with different settings and specify which of them is the default. Policies for detection engines - using profiles (see above), they enable different configurations and rules for scanning files in packages, including skipping scanning. Policies for size limits - allow different limits on the size of packages and files uploaded by different users or groups. Policies for package expiration - allow setting different expiration times for different users and groups.
Support for user distribution groups. It allows the administrator to mark a user group as a distribution group and enter an email for it. Distribution groups are then offered to users (depending on the settings to all users, or only to those from the group) to fill in where contacts are entered, similarly to records from the user’s personal address book. In other words, it is possible to send packages “to a group” that the administrator has prepared for users. New Search function in Settings - Configuration for administrators. In the top right, there is a new field for searching in configuration (shortcut Ctrl+K), which enables quick search and jump to the desired option. Ability to sign in an administrator via ADFS or OIDC (like MS Entra). Until now, it was only possible with a local account in the application. The administrator can allow users new options for packages in quarantine, specifically: In the section “Configuration - Packages - Access control” an option “Users can delete files in packages in quarantine” was added with a note that deleting the last file in quarantine will automatically release the package from quarantine. Similarly, an option “Users can add and manage package files in quarantine” was added. A suitable addition if the mode “Allow download of clean files from quarantined packages” is set. It allows users to add and move files even in packages in quarantine.
Expiration/deletion of individual files in a package. Previously, automatic expiration applied only to the entire package with all files. The new version allows setting file expiration in a package independently of the expiration of the entire package. Either from file creation or from the last access to the file. Suitable especially for longer-used or persistent cooperative packages with subfolders and a large amount of content. Notifications for packages and requests can be sent with the sender’s email included (controlled by the administrator in Settings - Configuration - E-mail). Specifically, the Reply-To header is set in the message, which does not break SPF/DKIM/DMARC. A “Network objects” catalog was introduced, where the administrator can define and name IP addresses, ranges, and their groups. These can currently be used for: Different login forms (buttons) for different IP ranges. Based on IP ranges, it is possible to determine which ADFS or OIDC sources are displayed in the login form, i.e., internal network can have different (ADFS) than from the Internet (MS Entra), etc. Detection engine policies.
Ability to globally disable sending of all emails from the application (in Settings - Configuration - E-mail - Send emails).
Minor changes: Requests have been adjusted, but with emphasis on minimal impact on users. Specifically, the following changes: Terminology - previously: Request to submit a package, now: Request files upload. However, the user still uses the same menu Send request to create it and essentially an identical form. Requests are no longer displayed in Received packages of the user who created/sent them, but in Sent packages and additionally in the new menu Requests. Technically, the request is now created as a new empty package of the user, to which an access link (see new features above) is created immediately with corresponding parameters (upload-only, limited to one access, optional password) to mirror the behavior of the original requests.
The administrator can disable sending package notifications for a user (in the user’s profile/detail in the user list). Suitable for system/API accounts so that emails that nobody wants/reads are not sent to them. The user has the option to disable sending the notification for a new package (in the New package form), similarly to a request. The information and access link to the package must then be passed to recipients by the user in another way. The administrator can remove even individual files from quarantine, not only the whole package. Suitable if the mode “Allow download of clean files from quarantined packages” is set. The administrator can now change basic package properties, same as the user: i.e., name, note, and validity. In the administrators list, a preview of permissions is displayed like for users directly in the list. Email templates improved: they better reflect cooperative packages, persistent packages, additional file additions, public packages with a password, etc. New template for sharing package content (access links). API v2 changes: Support for managing user groups added. Pagination and basic filtering added in user and group lists. For administrator API tokens, a setting “User impersonation enabled” was introduced, which determines whether the administrator token also allows performing user actions on behalf of a user. Previously, it was always allowed.
In the API tokens section, the administrator can reissue an existing API token. The old token is invalidated and a new one is issued and displayed one-time. Previously, it was necessary to delete the token and create a new record, which lost token linking and settings. Display of packages in the queue adjusted. Previously, only new packages still waiting for inspection were shown here. Now, all packages that have files waiting for inspection are shown (e.g., newly added files into an old package). A session was introduced when adding and uploading files into a package. It prevents conflicts during simultaneous uploads into one package from multiple sources, allows correctly canceling unfinished/failed uploads, etc. It is transparent for users, they do not need to handle or know anything, it happens automatically. When creating a new user by an administrator, the default is to send a link to set a password instead of manually entering a password (but it is still possible to switch). A new permission “Reset password” was added, without which a local user cannot request a password reset. After the upgrade, all users who had login permission will automatically receive it, so the behavior does not change. Improved package size limits so they work not only for the first upload but also for ongoing edits. New submenu “User management” in the Settings menu, to which parts related to managing users, groups, administrators, etc. were moved. Better options for updating password hashes, specifically: Historically, the algorithm (or its parameters) for calculating password hashes has already changed several times to meet current recommendations. However, this only manifested when changing the password of an existing user or creating a new user. Now, if needed, the password hash is automatically updated to the current version of the algorithm upon user login. In addition, accounts with an outdated password hash are indicated to the administrator in the user and administrator list. The administrator can, for example, send them a password reset link to force the update.
The feature “Store password hashes” in Active Directory settings was removed. It could have unexpected consequences for some (during AD outage/maintenance/error, sign-in could work even if the account was meanwhile removed in AD, password changed, etc.). In the permission settings dialog (for user groups), there may be exclamation marks warning that this permission is now not used due to the application settings. It now includes a link and allows jumping directly to the corresponding part of settings so this can be changed. In the briefcase, the option to set a package password was removed (intended for sending “to yourself”). The AFiT module supports setting subdirectories for input and output. Support for RHEL 10 and compatible clones added for installation and running the application. Addition of a CLI script for importing and creating users from CSV. Improved evaluation of the last update for antiviruses and addition to the Dashboard screen. Addition of totals to the chart on the Dashboard screen. Tolerance for the validity time of TOTP codes was introduced when signing in with an additional factor. The administrator can set in Settings - Configuration - Users - Multi-factor authentication - TOTP time delay [s] in the range 0 to 30 and the default is 10 s. Package states “requested” and “uploading” were removed. This is related to the new features and changes above (access links, modified requests). It is now possible to enable and disable sending error reports (exceptions), or anonymize it (Settings - Configuration - Diagnostics). It is also possible to enable or disable sending basic information about the application environment (during regular license checks). We recommend keeping it enabled for better diagnostics of errors and compatibility. Change in evaluating available actions on objects in the web interface (e.g., packages), the frontend now dynamically adapts to the backend. For new installations, Let’s Encrypt certificate support was reworked. Use of “Certbot” was discontinued; the native nginx acme plugin is now used. Existing installations will remain unchanged. In Settings - Configuration - SFTP server, the static top warning about needing to have the sofie-sftp-server service enabled was replaced with a dynamic message that reflects the actual state of this service (whether it is running). The administrator can now switch the account type between local and remote in the user and administrator lists. Previously, in case of change it was necessary to delete the account and create it again as the desired type (local manually, remote left to be created automatically upon the user’s first sign-in). It should be used only in specific cases, for example if the administrator needs to prepare some settings for an account, creates it locally manually and then switches it to remote. Unauthorized attempts to access the application are now logged (blocked due to Settings - Configuration - Security - Access restriction) - at DEBUG level. The number of these logs per time can be limited in Settings - Configuration - Logging - Limit logging of unauthorized access attempts, to prevent log flooding (by default the limit is enabled to 3 per 60 seconds. Internal development changes: updates to internal libraries and dependencies were performed, refactoring of permission evaluation for actions within the application, refactoring of texts and translations, and others.
Fixes: Some entries in the audit log (e.g., about changing the user’s email/alias) did not have the source/account that performed the action filled in. Fixed. Manual cancellation of uploading previously showed it was canceled, but in the background it could still continue and might not be correctly “cleaned up”. Introducing upload sessions, see above, solves this. Improved dialogs for password check and limited number of accesses to a package, including fixing a bug where direct access to the link for adding a file to a package skipped these dialogs and the file could not be added. Removed found inconsistencies between the documentation and the API v2 implementation. Reduced the amount of SSE notifications backend->frontend, which removes unnecessary flickering (reloading) of the page in some situations. Fixed that in package lists from the administrator’s perspective, the ! icon with a warning that the package is not encrypted was incorrectly displayed even though encryption is enabled, also for empty packages (without files), where this did not make sense. Via SFTP, it is no longer possible to access a password-protected package because there is no way to enter this package password in the SFTP channel. Export of users to CSV was incorrectly limited by the set pagination; it is now limited by a maximum of 5000 records. Other various fixes, especially texts, appearance, function of some filters, etc.
|