Object validity checks in public networks #1005

New issue

Open

opened 2025-12-28 17:21:27 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:21:27 +00:00

Owner

Originally created by @roman-khimov on GitHub (Apr 11, 2023).

I'm always frustrated when I'm looking at #2287 (especially at https://github.com/nspcc-dev/neofs-node/pull/2287#discussion_r1142664231 part of it). We need to replicate an object, but in general there are zero chances for a receiving node to check its validity wrt current (or past!) container permissions. Storage nodes are special, OK, they have some bits set for their verbs in containers, but this allows them for example to add some objects that were never created by the user.

Describe the solution you'd like

I don't have any for now, other than some real metadata service.

Originally created by @roman-khimov on GitHub (Apr 11, 2023). ## Is your feature request related to a problem? Please describe. I'm always frustrated when I'm looking at #2287 (especially at https://github.com/nspcc-dev/neofs-node/pull/2287#discussion_r1142664231 part of it). We need to replicate an object, but in general there are zero chances for a receiving node to check its validity wrt current (or past!) container permissions. Storage nodes are special, OK, they have some bits set for their verbs in containers, but this allows them for example to add some objects that were never created by the user. ## Describe the solution you'd like I don't have any for now, other than some real metadata service.