Ciao and thank you for the reply.
I created the datasets structure at first with generic (so root as owner and the default stuff) and then I applied the ACL starting from comune with read and no inherit + recursive unchecked.
Same for prova-0.
Then I moved to prova-01 and I set the preset modify + inherit + recusive
As I understood during these tests, the option modify includes delete so, if I leave like so, the user can delete the folder prova-01.
This is what happens by set / unset the delete children and delete options
| delete children | delete | prova-1 del |
del files / folder in prova-1 created by same group |
del files / folder in prova-1 created by other group |
|---|---|---|---|---|
| set | unset | no | yes | yes |
| unset | set | yes | yes | yes |
| unset | unset | no | yes | no |
| set | set | yes | yes | yes |
for the replication task instead I followed this old video from @LTS_Tom where he uses the encrypted dataset for source and destination.
As you can see, on the destination the data replicated will be accessible only with the key of the source. So on destination you will need dataset-pool key + replicated-dataset key
I think that to access the data replicated the sw will have to decode 2 times and could this affect performance or something?