A clock skew fix has been implemented to address a specific issue where newly issued v2 session tokens were being rejected due to a slight drift in the clock between the validating node and the issuer. Additionally, a parsing bug has been fixed in the gateway that was causing empty rules to be returned instead of properly handling GETRANGEHASH records in container EACL. This issue was initially addressed in REST Gateway v0.19.1 by gracefully skipping unsupported operations.
Furthermore, object uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes will now be rejected with an HTTP 400 status code to prevent malformed expiration metadata from entering the storage network. The support for RANGE EACL operations has been completely removed, and the NeoFS SDK Go dependency has been upgraded from RC22 to RC23, along with updates to kin-openapi, viper, and grpc dependencies.
Panel v0.11.1 Enhancements
The NeoFS Panel, which can be accessed at panel.fs.neo.org, has received compatibility and security improvements in version 0.11.1. This release includes updates to ensure compatibility with S3 Gateway 0.47.0 and the latest authboxsrv credential service, following the addition of S3 credential issuance in Panel v0.11.0.
Security measures have been strengthened by restricting object previews to safe content types and addressing a prototype pollution vulnerability related to building the object tree. The release also improves the handling of failed metadata fetches and network error states.
Several fixes have been implemented to enhance wallet and session reliability:
- Withdrawals now accept fractional GAS amounts.
- Wallet selection is now correctly restored after canceling a NeoLine connection.
- Session restoration in OneGate has been fixed in case of WalletConnect initialization failure.
- Profile loading no longer stalls after unsuccessful requests.
- The S3 credentials dialog can now be closed before issuance is complete.
Additionally, a fix has been applied to prevent unintended EACL rule changes during drag-and-drop operations, and token validation now accurately displays signing status for expired tokens and missing permissions. Similar to the REST Gateway, support for RANGE EACL operations has been removed, and the Docker build image has been upgraded to Node 22.
GetRange Removal Process
The removal of RANGE EACL from both tools marks the completion of a cleanup process across various NeoFS components. Node v0.57.0 eliminated the GetRange object service method, SDK RC22 removed GetRangeHash, and now the REST Gateway and Panel have removed RANGE from EACL handling as the operation is no longer part of the protocol.
For more information, you can access the release notes for Panel v0.11.1 at the following link: Panel v0.11.1 Release Notes
Similarly, the release notes for REST Gateway v0.20.0 can be found here: REST Gateway v0.20.0 Release Notes
