Neo SPCC published updates to NeoFS REST Gateway and Panel on Oct. 9. The releases complete the removal of RANGE EACL support across the NeoFS access layer. They also align both tools with the latest storage node and SDK releases. The changes focus on reliability fixes, security hardening, and stricter input validation.
REST Gateway v0.20.0
The REST Gateway acts as the HTTP bridge between web apps and NeoFS storage. Version 0.20.0 adds a container revision field to ContainerInfo. That exposes the versioning metadata introduced in Node v0.57.0, so REST clients can track container configuration changes.
A clock skew fix handles a problem where fresh v2 session tokens were rejected when a validating node’s clock drifted slightly from the issuer’s. The gateway also fixes a parsing bug that returned empty rules instead of handling GETRANGEHASH records in container EACL. That issue was first mitigated in REST Gateway v0.19.1 by skipping unsupported operations gracefully.
Uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes are now rejected with an HTTP 400 status. This prevents malformed expiration metadata from entering the storage network. RANGE EACL operation support has been removed entirely. The NeoFS SDK Go dependency moved from RC22 to RC23, with updates to kin-openapi, viper, and grpc.
Panel v0.11.1
The NeoFS Panel at panel.fs.neo.org gets compatibility and security improvements in v0.11.1. The release updates the Panel for S3 Gateway 0.47.0 and the updated authboxsrv credential service. It follows the S3 credential issuance feature added in Panel v0.11.0.
Security work restricts object previews to safe content types only. It also fixes a prototype pollution vulnerability when building the object tree. Failed metadata fetches and network error states are handled more carefully.
Several wallet and session fixes target daily usability. One fix prevents unintended EACL rule changes during drag-and-drop operations. Token validation now shows signing status correctly for expired tokens and missing permissions. As with the REST Gateway, RANGE EACL support is gone. The Docker build image has been upgraded to Node 22.
GetRange removal arc
The RANGE EACL removal in both tools completes a cleanup across multiple NeoFS components. Node v0.57.0 removed the GetRange object service method entirely. SDK RC22 dropped GetRangeHash. The REST Gateway and Panel now remove RANGE from EACL handling because the operation no longer exists in the protocol.
I think this batch is less about new features and more about closing old gaps. The Panel v0.11.1 notes are at https://github.com/nspcc-dev/panel-fs-neo-org/releases/tag/v0.11.1. The REST Gateway v0.20.0 notes are at https://github.com/nspcc-dev/neofs-rest-gw/releases/tag/v0.20.0. Users on older versions may want to check compatibility before upgrading.
The post Neo SPCC ships NeoFS REST Gateway v0.20.0 and Panel v0.11.1 appeared first on TheCryptoUpdates .
