You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
curl -vk -X POST -u marie:radioactivity https://host.docker.internal:9200/ocs/v1.php/apps/files_sharing/api/v1/shares/pending/<share-id>
Now as Marie share the resource back to user Einstein with role 17 (considering that Einstein is the owner of the resource feels a little weird that you can reshare the same resource to the owner with lower permission?)
The http status is 200 and ocs status is 996 with error message grpc create share request failed
log
curl -vk -X POST -u marie:radioactivity https://host.docker.internal:9200/ocs/v1.php/apps/files_sharing/api/v1/shares -d 'path=folder_from_einstein' -d 'shareType=0' -d'permissions=17' -d'shareWith=moss' -d'reshares=true' -d 'space_ref=1284d238-aa92-42ce-bdc4-0b0000009157$4c510ada-c86b-4815-8820-42cdf82c3d51!b979b13d-85fb-4ac1-ad13-576b12da553a' Note: Unnecessary use of -X or --request, POST is already inferred.* Trying 127.0.0.1:9200...* TCP_NODELAY set* Connected to host.docker.internal (127.0.0.1) port 9200 (#0)* ALPN, offering h2* ALPN, offering http/1.1* successfully set certificate verify locations:* CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs* TLSv1.3 (OUT), TLS handshake, Client hello (1):* TLSv1.3 (IN), TLS handshake, Server hello (2):* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):* TLSv1.3 (IN), TLS handshake, Certificate (11):* TLSv1.3 (IN), TLS handshake, CERT verify (15):* TLSv1.3 (IN), TLS handshake, Finished (20):* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):* TLSv1.3 (OUT), TLS handshake, Finished (20):* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256* ALPN, server did not agree to a protocol* Server certificate:* subject: O=Acme Corp; CN=OCIS* start date: Aug 4 09:32:18 2022 GMT* expire date: Aug 4 09:32:18 2023 GMT* issuer: O=Acme Corp; CN=OCIS* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.* Server auth using Basic with user 'marie'
> POST /ocs/v1.php/apps/files_sharing/api/v1/shares HTTP/1.1
> Host: host.docker.internal:9200
> Authorization: Basic bWFyaWU6cmFkaW9hY3Rpdml0eQ==
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Length: 202
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 202 out of 202 bytes* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):* Mark bundle as not supporting multiuse< HTTP/1.1 200 OK< Content-Length: 164< Content-Type: text/xml; charset=utf-8< Date: Thu, 04 Aug 2022 10:27:17 GMT< Ocs-Api-Version: 1< Vary: Origin< <?xml version="1.0" encoding="UTF-8"?>* Connection #0 to host host.docker.internal left intact<ocs><meta><status>error</status><statuscode>996</statuscode><message>grpc create share request failed</message></meta></ocs>%
But looks like the share is still created , if I go to the UI and check the resource's collaborator list as user einstein (owner of the resourceMoss is listed twice with roleviewerandeditor`
If I access the UI of Moss it gives me the option to accept or decline the again, also in share with indicator Moss is shown x times the resource has been shared, and the permission is still 31 I think because I can create resources
Upon sending the Get req to fetch the shares received by Moss the reshare from Marie is listed even though the API threw error message
curl -vk -X GET -u moss:vista https://host.docker.internal:9200/ocs/v1.php/apps/files_sharing/api/v1/shares\?shared_with_me\=true
I just went through the above steps. And for me it already fails at step 6 with the current code. Marie can't reshare Einstein's folder with Einstein
6. Now as Marie share the resource back to user Einstein with role 17 (considering that Einstein is the owner of the resource feels a little weird that you can reshare the same resource to the owner with lower permission?)
It seems that all of the share managers in reva already dis-allowed to reshare a resource with the owner of that resource. Apart from the "cs3" manger which was our default from beta4 to beta7.
"cs3" should be fixed with the above PR.
But we will also switch the default again (to "jsoncs3"), which has the check as well.
C0rby
pushed a commit
to cs3org/reva
that referenced
this issue
Sep 12, 2022
Describe the bug
A clear and concise description of what the bug is.
Steps to reproduce
Steps to reproduce the behavior:
Einstein
create resourcefolder_from_einstein
Moss
with permission31
Moss
accept the shareMoss
reshare the recently accepted share to userMarie
with permission17
Marie
accept the shareMarie
share the resource back to userEinstein
with role17
(considering that Einstein is the owner of the resource feels a little weird that you can reshare the same resource to the owner with lower permission?)einstein
accept the shareEinstein
create a folder inside the reshared folder inside theShare jail
(Note this folder is shared with role viewer)log
Similarly, If you go one level inside
TestFolder
, you can create/upload/delete/.... resources even from the UIMarie
reshare the same resource to userMoss
(the user that she got share from) with permission17
The
http
status is200
andocs
status is996
with error messagegrpc create share request failed
log
But looks like the share is still created , if I go to the UI and check the resource's collaborator list as user
einstein
(owner of the resourceMoss is listed twice with role
viewerand
editor`Moss
it gives me the option toaccept
ordecline
the again, also in share with indicatorMoss
is shown x times the resource has been shared, and the permission is still31
I think because I can create resourcesGet
req to fetch the shares received byMoss
the reshare fromMarie
is listed even though the API threw error messagelog
Expected behavior
owner
with permission lower than what the owner already has.reshare
the resource with owner with lower perm the permission should be followed properlyActual behavior
As described in the steps to reproduce
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.
OCIS=latest
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: