A clock skew fix has been implemented to address an issue where newly issued v2 session tokens were being rejected due to slight clock drift between the validating node and the issuer. Additionally, a parsing bug has been fixed in the gateway to properly handle GETRANGEHASH records in container EACL, which was first addressed in REST Gateway v0.19.1 by gracefully skipping unsupported operations.
Object uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes will now result in an HTTP 400 status, preventing malformed expiration metadata from entering the storage network. The support for RANGE EACL operations has been 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
The NeoFS Panel, which can be accessed at panel.fs.neo.org, has received compatibility and security enhancements in version 0.11.1. This release includes updates to ensure compatibility with S3 Gateway 0.47.0 and the updated authboxsrv credential service, following the addition of S3 credential issuance in Panel v0.11.0.
Security measures have been implemented to restrict object previews to safe content types and address a prototype pollution vulnerability in the object tree building process. The release also strengthens the handling of failed metadata fetches and network error states.
Several improvements have been made to enhance wallet and session reliability:
- Withdrawals now accept fractional GAS amounts.
- Wallet selection is now properly restored after cancelling a NeoLine connection.
- OneGate session restoration has been fixed in case of WalletConnect initialization failure.
- Profile loading will no longer stall after failed requests.
- The S3 credentials dialog can now be closed before issuance is complete.
An additional fix has been implemented 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 has been removed. The Docker build image has been upgraded to Node 22.
GetRange removal arc
The removal of RANGE EACL in both tools marks the completion of a cleanup process that spans across multiple NeoFS components. Node v0.57.0 removed the GetRange object service method, SDK RC22 dropped 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 further details, the release notes for Panel v0.11.1 can be accessed 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
