nspcc-dev/send-fs-neo-org
1
0
Fork 0
mirror of https://github.com/nspcc-dev/send-fs-neo-org.git synced 2026-03-01 04:29:27 +00:00
Code Issues 1 Projects Packages Wiki Activity

Send privately #15

New issue
Open
opened 2025-12-28 18:13:46 +00:00 by sami · 2 comments
sami commented 2025-12-28 18:13:46 +00:00
Owner
Copy link

Originally created by @roman-khimov on GitHub (May 12, 2023).

We can add "send privately" function to send.fs.neo.org to make objects available only to users logged in with specified e-mail addresses. It can work by attaching additional attributes ("Receiver") and generating bearer token that allows GETs if there is a match (default EACL should prohibit GETting objects with this attribute). Some additional auth/non-auth redirecting URL might be needed as well.

Originally created by @roman-khimov on GitHub (May 12, 2023). We can add "send privately" function to send.fs.neo.org to make objects available only to users logged in with specified e-mail addresses. It can work by attaching additional attributes ("Receiver") and generating bearer token that allows GETs if there is a match (default EACL should prohibit GETting objects with this attribute). Some additional auth/non-auth redirecting URL might be needed as well.
sami commented 2025-12-28 18:13:46 +00:00
Author
Owner
Copy link

@roman-khimov commented on GitHub (May 12, 2023):

Related to nspcc-dev/neofs-api#256, even though can be expressed now with

get receiver != "" -> deny
get * -> allow

primary EACL table and

get receiver == user@domain -> allow
get receiver != "" -> deny
get * -> allow

bearer.

@roman-khimov commented on GitHub (May 12, 2023): Related to nspcc-dev/neofs-api#256, even though can be expressed now with ``` get receiver != "" -> deny get * -> allow ``` primary EACL table and ``` get receiver == user@domain -> allow get receiver != "" -> deny get * -> allow ``` bearer.
sami commented 2025-12-28 18:13:46 +00:00
Author
Owner
Copy link

@roman-khimov commented on GitHub (Aug 19, 2024):

Not before we solve https://github.com/nspcc-dev/panel-fs-neo-org/issues/174.

@roman-khimov commented on GitHub (Aug 19, 2024): Not before we solve https://github.com/nspcc-dev/panel-fs-neo-org/issues/174.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/139-adjust_for_timebound_epochs
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2.1
v0.6.2
v0.6.1
v0.6.0
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.2.6
v0.1.8
v0.1.7
v0.0.2
v0.0.1
Labels
Clear labels   
I1

   
I2

   
I3

   
I4

   
S2

   
S3

   
S4

   
U0

   
U1

   
U2

   
U4

   
bug

   
enhancement

   
epic

   
feature
No labels
I1
I2
I3
I4
S2
S3
S4
U0
U1
U2
U4
bug
enhancement
epic
feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/send-fs-neo-org#15
No description provided.