nspcc-dev / nspcc-dev/neofs-node
Object validity checks in public networks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #2287 and the referenced discussion in PR #2287 to understand the replication and permission-validation context. The issue does not identify files, tests, an entry point, or an agreed solution; progress would first require defining the metadata service and the validity checks it must provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100