Neo SPCC releases NeoFS REST Gateway v0.20.0, Panel v0.11.1

A clock skew repair addresses a problem the place freshly issued v2 session tokens have been rejected when the validating node’s clock drifted barely from the issuer’s. The gateway additionally corrects a parsing bug that returned empty guidelines as an alternative of correctly dealing with GETRANGEHASH information in container EACL, a problem first mitigated in REST Gateway v0.19.1 by skipping unsupported operations gracefully.

Object uploads with non-numeric __NEOFS__EXPIRATION_EPOCH attributes are actually rejected with an HTTP 400 standing, stopping malformed expiration metadata from getting into the storage community. RANGE EACL operation assist has been eliminated solely, and the underlying NeoFS SDK Go dependency has been upgraded from RC22 to RC23, alongside updates to a number of different dependencies together with kin-openapi, viper, and grpc.

Panel v0.11.1

The NeoFS Panel, accessible at panel.fs.neo.org, receives compatibility and safety enhancements in v0.11.1. The discharge updates the Panel for compatibility with S3 Gateway 0.47.0 and the up to date authboxsrv credential service, following the S3 credential issuance characteristic added in Panel v0.11.0.

Safety hardening consists of limiting object previews to secure content material sorts solely and fixing a prototype air pollution vulnerability when constructing the item tree. The discharge additionally hardens dealing with of failed metadata fetches and community error states.

A number of pockets and session reliability fixes deal with sensible usability points:

• Fractional GAS quantities now accepted for withdrawal.
• Pockets choice corrected after canceling a NeoLine connection.
• OneGate session restoration mounted when WalletConnect initialization fails.
• Profile loading now not stalls after failed requests.
• S3 credentials dialog can now be closed earlier than issuance completes.

A further repair prevents unintended EACL rule adjustments throughout drag-and-drop operations, and token validation has been corrected to correctly show signing standing for expired tokens and lacking permissions. As with the REST Gateway, RANGE EACL assist has been eliminated. The Docker construct picture has been upgraded to Node 22.

GetRange elimination arc

The RANGE EACL elimination in each instruments completes a cleanup that spans a number of NeoFS elements. Node v0.57.0 eliminated the GetRange object service methodology solely, SDK RC22 dropped GetRangeHash, and the REST Gateway and Panel now take away RANGE from EACL dealing with because the operation now not exists within the protocol.

The Panel v0.11.1 launch notes may be discovered on the hyperlink beneath:
https://github.com/nspcc-dev/panel-fs-neo-org/releases/tag/v0.11.1

The REST Gateway v0.20.0 launch notes may be discovered on the hyperlink beneath:
https://github.com/nspcc-dev/neofs-rest-gw/releases/tag/v0.20.0