Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Satellite UI][Accesses] Created access grant does not decrypt existing objects #5112

Closed
AlexeyALeonov opened this issue Aug 25, 2022 · 4 comments
Labels
Bug Something isn't working

Comments

@AlexeyALeonov
Copy link
Contributor

AlexeyALeonov commented Aug 25, 2022

Description

I have opened my buckets via satellite UI Buckets view using the encryption phrase 123, uploaded some objects. Then created an access grant with the full access and encryption phrase 123. This access grant doesn't allow me to see uploaded files neither via uplink nor Filezilla

Screenshots

image

now with the access grant created with the same encryption phrase:

$ uplink ls --access 1cCYAHeo... ls sj://test
(empty)

Steps to reproduce the issue:

  1. Open Buckets with the simple encryption phrase (to be confident that you did not any mistake)
  2. Upload some objects
  3. Create an access grant in the satellite UI using the exactly the same simple encryption phrase
  4. Try to list objects with this access grant with uplink ls --access 1cCYAHeo... sj://test

Describe the results you expected:
I should be able to see objects using an access grant with the same encryption phrase

Describe the results you received:
I cannot see objects using an access grant with the same encryption phrase

Additional information you deem important (e.g. issue happens only occasionally):
The access grants created earlier are working normally. Access grants, created in uplink using an API Key are working normally too.
Access grants created in the satellite UI with the same encryption phrase are compatible with each other, but incompatible with old ones (with the same encryption phrase) and Buckets view.

Your environment

  • Operating system and version: Windows 10 Pro, Ubuntu 20.04 LTS
  • Additional environment details (Raspberry PI, Docker, VMWare, etc.):
$ uplink version
Release build
Version:            v1.62.3
Build timestamp:    23 Aug 22 18:04 EEST
Git commit:         88dffc8d3d341f57443a3fcaf3e7b1f749a0d781

PATH                      VERSION
storj.io/storj            (devel)
storj.io/common           v0.0.0-20220719163320-cd2ef8e1b9b0
storj.io/drpc             v0.0.32
storj.io/monkit-jaeger    v0.0.0-20220726162929-c3a9898b5bca
storj.io/private          v0.0.0-20220801080548-639387a299f7
storj.io/uplink           v1.9.1-0.20220623122820-25d79c31a876

gz#19541

gz#19558

@AlexeyALeonov AlexeyALeonov added the Bug Something isn't working label Aug 25, 2022
@storjrobot
Copy link

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/topic/19479/7

@AlexeyALeonov
Copy link
Contributor Author

affects gz#19541 too

@storjrobot
Copy link

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/sharing-options/19448/4

@Erikvv
Copy link
Contributor

Erikvv commented Aug 30, 2022

As far as I can see the conversion from passphrase to access grant is done in the browser. So I think it should first be explored if it is a front-end issue.

I asked around. This was fixed through 3019ad3 which was deployed in a hotfix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants